As recommended by the Gnome-shell developers a bug upstream with Mutter is
opened.
https://gitlab.gnome.org/GNOME/mutter/-/issues/1356
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1356
https://gitlab.gnome.org/GNOME/mutter/-/issues/1356
--
You received this bug notification be
Also I'm happy to use a workaround. I'm just a bit disappointed that devilspie
no longer works.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1888098
Title:
Ubuntu 20.04 gnome-s
Thank you for your further input Daniel.
The issue is that the stable version of ChromisPOS that I'm using the
source code was destroyed by a commit error.
I'm working together with the developer providing resources to get the
unstable version production ready but that is taking more time than I
Reported this Upstream under
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3011
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3011
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3011
--
You received this bug notification because you are a member of Desktop
Packa
This is interesting. When running gnome-shell in Wayland the window
placement seems to be correct. I've been testing it a bit.
Unfortunately Wayland doesn't allow for remote desktop access so I can't
help my customers when something goes wrong.
--
You received this bug notification because you a
Wish me luck, fingers crossed. I'm going to create the issue on Gnome's
bug tracker now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1888098
Title:
Ubuntu 20.04 gnome-shell pla
@Daniel van Vugt
Thanks for your understanding and advice.
Do you have any recommendations for an alternative window manager that is:
- Officially Supported by Canonical under the support contract
- Touchscreen Friendly
- Secure
- Has a sidebar on the left (the product I sell is designed around t
And the cashier side
** Attachment added: "Cashier side of the setup"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394700/+files/Bug1888098_opposingScreensCashier.jpeg
--
You received this bug notification because you are a member of Desktop
Packages, which
And before anyone starts anything about freeloading.
I donate several thousand euros per year and a lot of my time to open
source projects.
So, let's not go there.
Once again thank you.
I hope that it's much clearer now what is not working as expected in
Ubuntu 20.04's iteration of Gnome Deskto
So you can see what the system looks like when installed
** Attachment added: "Opposing Screens Customer"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394699/+files/Bug1888098_opposingScreensCashier.jpeg
--
You received this bug notification because you are
Some more fun, the onscreen keyboard follows the misplaced dialog box to
the non-touchable monitor.
** Attachment added: "Screen Keyboard opens on non touchable area"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394696/+files/Bug1888098_ScreenKeyboardOnNonTou
And here is proof that there are no extensions enabled
** Attachment added: "No Extensions enabled"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394697/+files/Bug1888098_ProofAllExtensionsDisabled.jpeg
--
You received this bug notification because you are a
Here is an extra treat so you can see why block Caribou is very
necessary and the gnome onscreen keyboard implementation makes the
system completely unusable.
** Attachment added: "Extra treat why the block caribou extension was on."
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1
Here is a photo so you can see that the Center New Window option does
nothing. At least it stopped doing the Easter Egg of putting things
halfway between two monitors that's a plus. :D
** Attachment added: "Photo Center new window doesn't do anything"
https://bugs.launchpad.net/ubuntu/+source/
Thanks for have a new look at this
Oh and I forgot to mention this is with the option
Center New Windows turned ON in Gnome Tweak Tool
Which should theoretically do the same as the DCONF edit line, right?
--
You received this bug notification because you are a member of Desktop
Packages, which
Here is a photo so it's easier to understand what the issue is.
** Attachment added: "Photo of the issue faced"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1888098/+attachment/5394688/+files/2020-07-21_Bug%20-1888098_GnomeWindowPlacementBug.png
--
You received this bug notifi
Removing the extensions has the same effect.
Block Caribou 36 is necessary as the Point of Sale system (Open source)
already has all the buttons and keyboard that are necessary for the use
of the Point of Sale system. Yet it contains text entry fields which pop
up the on-screen keyboard. There are
Public bug reported:
Ubuntu 20.04 LTS
gnome-shell:
Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2
What I expected to happen:
When clicking a button on the primary screen to open a new window in any
application, that window should always open on the same monitor.
What happened instead:
Gnome-shell i
There is a workaround via
xinput map-to-output "Weida Hi-Tech CoolTouch® System" eDP-1
There needs to be some kind of detection to do this automatically and
create a systemD systemctl file.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed t
Here is the xinput list-props while the second screen (AOC) is disconnected
Here the touch works as expected
xinput list-props 11
Device 'Weida Hi-Tech CoolTouch® System':
Device Enabled (169): 1
Coordinate Transformation Matrix (171): 0.50, 0.00, 0.50,
0.00, 1.
There is a regression of this bug in Ubuntu 20.04 using the default Gnome
desktop
Setup is a Shuttle POS P511
using a Weida CoolTouch controller with driver integrated into the Linux kernel
Second screen is a AOC USB-3.1 Display Link monitor without display
capabilities only (no touch).
When th
Done
https://github.com/storaged-project/udisks/issues/723
** Bug watch added: github.com/storaged-project/udisks/issues #723
https://github.com/storaged-project/udisks/issues/723
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-
The Source code file location where this happens I'm pretty sure is
here:
/src/disks/gduwindow.c
/*
*/
static void
eject_cb (UDisksDrive *drive,
GAsyncResult *res,
gpointer
Translation of the Error message to English:
Removal of the medium has failed
Error ejecting /dev/sdi: Command-line `eject"/dev/sdi"' exited with a non-zero
status 1:
eject: could not eject, last error:
Incorrect ioctl() for device
(udisks-error-quark, 0)
So you can see in the error message th
Public bug reported:
Use case: As a user of hot swap-able SATA disks using a Harddrive Riser
over eSATA. I need a safe, easy and convenient way to remove the hot
swap-able SATA disk without rebooting and without having to go to the
command line.
When attempting to eject an harddisk or a solid sta
I can confirm that Martin Vysny's solution/workaround works in Ubuntu
18.04.1LTS.
(this was not the case in Ubuntu Alpha when I reported this bug)
Please note that you have to reboot (or log-off and logon again) for the
system-monitor to show up in the gnome-tweaks extensions page.
Time to say g
So here is the upstream answer:
Window decorations are client-side on wayland, that means they are just another
part of the application window the same way as the products you are viewing. We
cannot tell what parts of the window are decorations, or whether there are in
fact any decorations at
BTW> Workaround to the buttons on the right (which only makes sense for right
to left languages ) was to install Gnome-tweak tool.
In Left to Right languages having the buttons on the left means less
mouse travel on high res screens to click the button. This was just good
well thought out and tes
Reported upstream to the Gnome-shell devs
https://gitlab.gnome.org/GNOME/gnome-shell/issues/493
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1787288
Title:
gnome-shell window t
Example of search query that Nautilus refuses to sort.
** Attachment added: "Example of where nautilus is not sorting"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1698351/+attachment/5176511/+files/Selectie_012.png
--
You received this bug notification because you are a member of
Here is a PNG of the icon so you can see what it looks like if you are
also on 18.04 with this bug.
I used icotool -x pos.ico
to extract the icons from the .ico file as PNGs
** Attachment added: "PNG version of the icon"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+at
And interestingly enough. Nautilus also displays the preview of the file
as noise.
** Attachment added: "Nautilus also shows the icon as noise."
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+attachment/5176038/+files/Schermafdruk%20van%202018-08-16%2000-36-31.png
--
You
Here is a screenshot of the icon in gnome-hell
** Attachment added: "Corrupted Icon"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+attachment/5176036/+files/Schermafdruk%20van%202018-08-16%2000-33-47.png
--
You received this bug notification because you are a member of
And here is the actual .ico file
** Attachment added: "the pos.ico file referred to by the desktop file"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787294/+attachment/5176037/+files/pos.ico
--
You received this bug notification because you are a member of Desktop
Packages, w
Public bug reported:
Steps to reproduce
Create an .ico file (for using the same icon between multiple platforms)
create a desktop file linking to the ico file.
here is an example of the one that doesn't work
[Desktop Entry]
Type=Application
Version=0.9.4
Name=ChromisPos
Comment=Chromis Point of
See here in this screenshot. The 50px are used for the Application which
is much more important than gnome-shell.
** Attachment added: "Opera browser gets rid of the title bar when maximized."
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787288/+attachment/5176025/+files/Scherma
See the screenshot
50px have been wasted here!
On my 1280x1024 production screens for my business 50px is an extra line of
text. Two if I use a smaller font.
I noticed that the Opera browser has figured out a way around this and
hides the unnecessary title bar when maximized. Maybe we can learn f
Public bug reported:
Steps to reproduce
Start Ubuntu
Login to Unity
Choose logoff
Choose Ubuntu (which should have the label Gnome-hell)
Note this is the only way to get Gnome-hell to start, starting it
directly just shows a black screen and dumps you back to the greeter.
(already created a bug r
Public bug reported:
Steps to reproduce
Switch to LightDM
Switch to Unity
(gnome wouldn't let me log in so I was looking for the log file)
Open Nautilus
in the search bar type ".log" (without the quotes)
All the log files in your home directory are shown
Click on Name column
nothing happens
click
Public bug reported:
== Release ==
Description:Ubuntu 18.04 LTS
Release:18.04
Ubuntu Gnome desktop
gdm login manager
== Package version ==
vino:
Geïnstalleerd: 3.22.0-3ubuntu1
Kandidaat: 3.22.0-3ubuntu1
Versietabel:
*** 3.22.0-3ubuntu1 500
500 http://nl.archive.ubun
Didn't help after all. Plymouth is still using 100% CPU on reboot.
Now trying all the suggestions in
https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1536771
Disabled plymouth in Grub and dpkg-reconfigured it.
--
You received this bug notification because you are a
I found the conflict with the eGalax Touch Daemon driver.
I moved the driver startup from /etc/init.d/eGtouch.sh
to userspace as I don't need the touchscreen at login.
The strange thing is I have 17 machines with this configuration and only
one is exhibiting this behaviour with plymouthd
--
Y
I've attached an apport report of the runaway process
** Attachment added: "apport.plymouth.b8ut5mm8.apport"
https://bugs.launchpad.net/lightdm/+bug/1192051/+attachment/5103196/+files/apport.plymouth.b8ut5mm8.apport
--
You received this bug notification because you are a member of Desktop
Pa
There is a regression of this bug in 16.04.4LTS
Linux computer 4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename: xenial
PID USER PR NIVIRTRES
Public bug reported:
Steps to reproduce:
* In the Gnome Disk Utility
* Select any drive supporting SMART
* click on the gear icon
* Choose SMART Info and Selftests
* Click on the dividing line between Attribute and Value
* Try to drag left or right in order to be able to read the Attribute
* Does
Regression in 16.04.2 this bug has come back. Using Intel i915 driver on
a Intel J3160 processor.
Connection is dual monitor VGA + HDMI
What do you need qua logging or actions to solve this issue?
** Attachment added: "Mouse Pointer Trails"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug
Problem still exists in Trusty:
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: Gck: gck_module_new:
assertion 'funcs != NULL' failed
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: module_instances:
assertion 'module' failed
Dec 20 13:17:37 hostname gnome-keyring-daemon[24288]: egg_
Solved by using the proprietary non-free driver from eGalax
http://www.eeti.com.tw/drivers_Linux.html
OpenSource and multiple displays where one is a touchscreen still don't
get along very well yet.
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
** Attachment added: "here is an output from /proc/bus/input/devices"
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1377857/+attachment/4278686/+files/IIyama-T1931SAW_egalax_notes.txt
--
You received this bug notification because you are a member of Desktop
Packages,
I have now 3 IIyama touchscreens with eGalax touchpanels the:
2x IIyama T1931-SR-b (5 wire resistive)
IIyama T1931-SAW-b (Acousic Wave)
The 1st screen (SR) worked out of the box and retained it's calibration but
needed a startup script and udev rule
# xinput list # to find the map-to-output v
Here is a video of the bug, LightDM ignores the settings and moves the pointer
to the right
https://drive.google.com/file/d/0B4c5GbInagPqZEZvUlQxZ01qX0U/view?usp=sharing
Here is a video of a working user session after logging in from LightDM,
proving that the script works.
https://drive.google.
Public bug reported:
Setup:
Ubuntu 14.04.1LTS
IIyama 19" Pro-Lite Touchscreen
Dell 17" regular monitor
Due to another bug in the detection of input devices I had to write a
script to tell Ubuntu which screen to use the touch from the
touchscreen.
so I put the following two entries into a basic b
Public bug reported:
Error message:
** (yelp:31227): WARNING **: Couldn't parse troff special character: 'dq'
runtime error: file /usr/share/yelp-xsl/xslt/common/icons.xsl line 139 element
call-template
The called template 'l10n.gettext' was not found.
runtime error: file /usr/share/yelp-xsl/xsl
53 matches
Mail list logo
