[Desktop-packages] [Bug 1724037] Re: Allow GNOME fractional scaling below 100%
@james-fsck you need to adapt the position values (x,y) as well to the scale as I outlined in the linked upstream issue: https://gitlab.gnome.org/GNOME/mutter/-/issues/1465#note_1582649 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1724037 Title: Allow GNOME fractional scaling below 100% Status in Mutter: New Status in gnome-control-center package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Bug description: It should be possible to scale down the whole shell to less than 100% e.g. 90% 85% etc. thanks ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 20:14:43 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1724037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864215] Re: Please add webp loader to gdk-pixbuf
** Bug watch added: Debian Bug tracker #951113 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951113 ** Also affects: debian via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951113 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1864215 Title: Please add webp loader to gdk-pixbuf Status in gdk-pixbuf: Unknown Status in gdk-pixbuf package in Ubuntu: Confirmed Status in gdk-pixbuf package in Baltix: Triaged Status in Debian: Unknown Bug description: Attempting to load a webp image -- for instance, https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp or https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file format" error. Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in libwebp, but isn't this really a gdk-pixbuf issue? If it really does belong to libwebp, my apologies, please dup this bug to 1407644 (I'm confident it doesn't belong to eog since I don't use that program; I have other programs that use libgdk-pixbuf). You can probably use eog to test this, or run /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i webp (I assume the loader would mention webp if there was a loader for it). I have these packages installed in addition to libgdk-pixbuf2.0-0: libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes the format: $ file /tmp/FKK78W.jpg.webp /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 1200x533, Scaling: [none]x[none], YUV color, decoders should clamp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 Date: Fri Feb 21 08:48:36 2020 InstallationDate: Installed on 2019-10-10 (133 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1864215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886272] Re: Request to package webp pixbuf
*** This bug is a duplicate of bug 1864215 *** https://bugs.launchpad.net/bugs/1864215 ** This bug has been marked a duplicate of bug 1864215 Please add webp loader to gdk-pixbuf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/1886272 Title: Request to package webp pixbuf Status in libwebp package in Ubuntu: Confirmed Bug description: It is not currently possible to open a WebP image in any standard application on Ubuntu (except Firefox). There is a now a small extension for gdk-pixbuf to support webp: https://github.com/aruiz /webp-pixbuf-loader Such extension has already been packaged for HEIF (heif-gdk-pixbuf), it'd be nice to have it for WebP too. Once installed, any standard Gnome program can support reading such image, and in particular, eog. An example file: https://www.gstatic.com/webp/gallery/1.webp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/1886272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 34813] Re: gedit fails to save files over smbfs/cifs
This bug also affects me. For another bug, I created instructions on how to reproduce my samba setup via docker: https://gitlab.gnome.org/GNOME/gedit/-/issues/322#steps-to-reproduce This might help reproducing this bug. ** Bug watch added: gitlab.gnome.org/GNOME/gedit/-/issues #322 https://gitlab.gnome.org/GNOME/gedit/-/issues/322 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/34813 Title: gedit fails to save files over smbfs/cifs Status in gedit: Expired Status in Samba Server: Invalid Status in SSHFS Mounter: Confirmed Status in gedit package in Ubuntu: Triaged Status in gedit package in CentOS: New Bug description: Saving files over a cifs/smbfs server doesnt work. You can open file, edit then save perfectly. But repeated saves after give you this error: "The file /home/dhonn/website/arrays.php has been modified since reading it. If you save it, all the external changes could be lost. Save it anyway?" The think is lying to me because I havent made any external changes. When I click "Save Anyway", i get this error: "Could not save the file /home/dhonn/website/arrays.php." But on the third try it works just fine. Here are the error messages, btw there are also GUI glitches too: http://dhonn.com/images/gedit-0.jpg http://dhonn.com/images/gedit-1.jpg To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/34813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864280] Re: software-properties-gtk removes [arch=amd64]
** Changed in: software-properties (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1864280 Title: software-properties-gtk removes [arch=amd64] Status in software-properties package in Ubuntu: Confirmed Bug description: When editing apt sources via software-properties-gtk, additional options like [arch=amd64] are removed. With more and more repositories deprecating i386, this problem becomes more and more important. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1864280/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 306673] Re: autofs timeout
I don't know how I can additionally link the following bug report in GNOME Gitlab: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1514 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1514 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1514 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/306673 Title: autofs timeout Status in Nautilus: Confirmed Status in nautilus package in Ubuntu: Triaged Bug description: Binary package hint: nautilus OS: Ubuntu 8.10 Intrepid, upgraded from Hardy Software: SSHFS, AutoFS, no changes concerning Nautilus I'm using SSHFS with AutoFS to mount remote shares, which I must have unmounted after some time because of security concerns. This has had me set a timeout on the AutoFS mounts. The problem is that when opening a remote folder in Nautilus, the timeout countdown starts as soon as I stop clicking on folders/files. When it's down, I get a password prompt. This is buggy behaviour to me, because if I set the timeout to 10 seconds, there is a password prompt every 10 seconds if I just have a remote folder open in Nautilus, doing nothing else. Of course I've got a bigger timeout, but it's still quite annoying. I think that it should either: 1. Start the timeout as soon as I don't browse around or poll the file system manually in any other way. Then ask for a password only if user interaction occurs. 2. Don't time out as long as I have an open remote folder (after closing the last remote directory, let AutoFS time out and unmount). This is how KDE's Konqueror and gnome-terminal behave. There is already a bug filed at the GNOME bugzilla about this. But it originates from 2002 and the last comment is from 2006... which is about the issue still not being resolved. That's why I'm reporting here. If anyone has a better idea who to harass into fixing this, speak up ;) Here's the GNOME bug: http://bugzilla.gnome.org/show_bug.cgi?id=101673 I've also started a thread at the ubuntuforums.org: http://ubuntuforums.org/showthread.php?t=1003656 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/306673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 306673] Re: autofs timeout
Not yet migrated to gitlab. ** Bug watch added: bugzilla.gnome.org/ #101673 https://bugzilla.gnome.org/show_bug.cgi?id=101673 ** Changed in: nautilus Importance: High => Unknown ** Changed in: nautilus Status: Confirmed => Unknown ** Changed in: nautilus Remote watch: GNOME Bug Tracker #101673 => bugzilla.gnome.org/ #101673 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/306673 Title: autofs timeout Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: Binary package hint: nautilus OS: Ubuntu 8.10 Intrepid, upgraded from Hardy Software: SSHFS, AutoFS, no changes concerning Nautilus I'm using SSHFS with AutoFS to mount remote shares, which I must have unmounted after some time because of security concerns. This has had me set a timeout on the AutoFS mounts. The problem is that when opening a remote folder in Nautilus, the timeout countdown starts as soon as I stop clicking on folders/files. When it's down, I get a password prompt. This is buggy behaviour to me, because if I set the timeout to 10 seconds, there is a password prompt every 10 seconds if I just have a remote folder open in Nautilus, doing nothing else. Of course I've got a bigger timeout, but it's still quite annoying. I think that it should either: 1. Start the timeout as soon as I don't browse around or poll the file system manually in any other way. Then ask for a password only if user interaction occurs. 2. Don't time out as long as I have an open remote folder (after closing the last remote directory, let AutoFS time out and unmount). This is how KDE's Konqueror and gnome-terminal behave. There is already a bug filed at the GNOME bugzilla about this. But it originates from 2002 and the last comment is from 2006... which is about the issue still not being resolved. That's why I'm reporting here. If anyone has a better idea who to harass into fixing this, speak up ;) Here's the GNOME bug: http://bugzilla.gnome.org/show_bug.cgi?id=101673 I've also started a thread at the ubuntuforums.org: http://ubuntuforums.org/showthread.php?t=1003656 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/306673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876518] Re: Gtk.Clipboard set_text() not working
** Bug watch added: gitlab.gnome.org/GNOME/pygobject/-/issues #405
https://gitlab.gnome.org/GNOME/pygobject/-/issues/405
** Also affects: pygobject via
https://gitlab.gnome.org/GNOME/pygobject/-/issues/405
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1876518
Title:
Gtk.Clipboard set_text() not working
Status in pygobject:
Unknown
Status in pygobject package in Ubuntu:
Incomplete
Bug description:
Writing to Gtk.Clipboard doesn't work (reading works).
Example code:
#!/usr/bin/python3
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk, Gdk
clipboard = Gtk.Clipboard.get(Gdk.SELECTION_CLIPBOARD)
clipboard.set_text("Does a text of all texts contain itself?", -1)
clipboard.store()
Ubuntu 20.04 with Gtk 3.36.0-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/1876518/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876518] [NEW] Gtk.Clipboard set_text() not working
Public bug reported:
Writing to Gtk.Clipboard doesn't work (reading works).
Example code:
#!/usr/bin/python3
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk, Gdk
clipboard = Gtk.Clipboard.get(Gdk.SELECTION_CLIPBOARD)
clipboard.set_text("Does a text of all texts contain itself?", -1)
clipboard.store()
Ubuntu 20.04 with Gtk 3.36.0-1
** Affects: pygobject (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1876518
Title:
Gtk.Clipboard set_text() not working
Status in pygobject package in Ubuntu:
New
Bug description:
Writing to Gtk.Clipboard doesn't work (reading works).
Example code:
#!/usr/bin/python3
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk, Gdk
clipboard = Gtk.Clipboard.get(Gdk.SELECTION_CLIPBOARD)
clipboard.set_text("Does a text of all texts contain itself?", -1)
clipboard.store()
Ubuntu 20.04 with Gtk 3.36.0-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1876518/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen
Tracked upstream with further information: https://github.com/micheleg /dash-to-dock/issues/1136 but should be resolved before release since Ubuntu Dock uses setting "Panel mode: extend to the screen edge". ** Bug watch added: github.com/micheleg/dash-to-dock/issues #1136 https://github.com/micheleg/dash-to-dock/issues/1136 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen Status in GNOME Shell: Unknown Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873525] Re: Gnome 3.36 with two monitors
*** This bug is a duplicate of bug 1869571 *** https://bugs.launchpad.net/bugs/1869571 ** This bug has been marked a duplicate of bug 1869571 Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1873525 Title: Gnome 3.36 with two monitors Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: After upgrading to 20.04, the "Activities" menu had display problems. Tracked upstream: https://github.com/micheleg/dash-to-dock/issues/1136 but should be resolved before release since Ubuntu Dock uses setting "Panel mode: extend to the screen edge". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1873525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869571] Re: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1869571 Title: Vertical dual monitor setup with main monitor on bottom causes overview to only use one eighth of screen Status in GNOME Shell: Unknown Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Very recently I have started experiencing a constant bug of the app overview / search functions of gnome shell being entirely unusable because shell operates at such a tiny scale that barely anything is shown on screen. I managed to narrow the problem down to having something to do with dual monitors, and then played around a bit with the settings. My results are that no matter what other configuration I set my two monitors in, gnome-shell operates perfectly. That is, if my secondary monitor is on the left, right or below my primary one, all is well. If, however, the secondary monitor is set to be on top of the primary one (As it physically is in my current setup), then the overview and app search functionality starts using some very weird kind of vertical scaling and becomes unusable. The window previews are so small that the (most of the time invisible) X button is bigger than the window itself, thus only making me able to close the windows instead of switching to them or moving them. Application search only shows half of the first row, the other half fading away. I am running Ubuntu 20.04 Focal Fossa (development branch) and version 3.36.0-2ubuntu1 of gnome-shell. Here are screenshots of my problem: The overview screen barely showing my open windows https://i.ibb.co/bJZFdR8/Kuvakaappaus-2020-03-29-14-14-22.png The search function only showing the top half of first row of icons https://i.ibb.co/g4qV3wP/Kuvakaappaus-2020-03-29-14-14-40.png When you mouse-over the windows many times over and over you might get the X button to show https://i.ibb.co/QjRKZr1/Kuvakaappaus-2020-03-29-14-18-07.png --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200220) Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: third-party-packages focal Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo tty uucp _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1869571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873525] Re: Gnome 3.36 with two monitors
Yes, it is the same problem. When additionally installing the _Dash to Dock_ extension from extensions.gnome.org, then you can easily change the settings (also from Ubuntu Dock). Unchecking the option "Panel mode: extend to the screen edge" (as noted in the link from my description: https://github.com/micheleg/dash-to- dock/issues/1136#issuecomment-603669287) makes the error disappear (but the dock is no longer full height). Also (as noted in the link in my description: https://github.com/micheleg/dash-to- dock/issues/1136#issuecomment-615452981), I am using two monitors with very different DPI. Therefore (also as noted in the same comment), it might be linked to https://bugs.launchpad.net/ubuntu/+source/gnome- shell-extension-ubuntu-dock/+bug/1826543. Answering your questions: 1. Upgrade to Ubuntu 20.04 (before it worked) 2./3. Did you even click on the link (https://github.com/micheleg/dash-to-dock/issues/1136#issuecomment-615452981)? There it is even documented with pictures! ** Bug watch added: github.com/micheleg/dash-to-dock/issues #1136 https://github.com/micheleg/dash-to-dock/issues/1136 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1873525 Title: Gnome 3.36 with two monitors Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: After upgrading to 20.04, the "Activities" menu had display problems. Tracked upstream: https://github.com/micheleg/dash-to-dock/issues/1136 but should be resolved before release since Ubuntu Dock uses setting "Panel mode: extend to the screen edge". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1873525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873525] [NEW] Gnome 3.36 with two monitors
Public bug reported: After upgrading to 20.04, the "Activities" menu had display problems. Tracked upstream: https://github.com/micheleg/dash-to-dock/issues/1136 but should be resolved before release since Ubuntu Dock uses setting "Panel mode: extend to the screen edge". ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1873525 Title: Gnome 3.36 with two monitors Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: After upgrading to 20.04, the "Activities" menu had display problems. Tracked upstream: https://github.com/micheleg/dash-to-dock/issues/1136 but should be resolved before release since Ubuntu Dock uses setting "Panel mode: extend to the screen edge". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1873525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792085] Re: MTP not working/very slow on Bionic
Same problem with Samsung Galaxy S6 on Ubuntu 19.04 and 19.10. When I try to connect/open in Nautilus, I get the error "Unhandled error message: The name 1.153 was not provided by any .service files". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: MTP not working/very slow on Bionic Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792167] Re: Display size detected incorrectly
Thanks a lot! I will investigate ways to correct this information: https://github.com/linuxhw/EDID/issues/4 ** Bug watch added: github.com/linuxhw/EDID/issues #4 https://github.com/linuxhw/EDID/issues/4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1792167 Title: Display size detected incorrectly Status in mutter package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: Invalid Bug description: My external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. It seems not related to the display server, compositor or window manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on Wayland). Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-09-05 (372 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: qtbase-opensource-src PackageArchitecture: amd64 Tags: bionic Uname: Linux 4.18.7-041807-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo vboxusers video voice _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792167] Re: Display size detected incorrectly
How can I check if the hardware is really sending faulty data or if it is just incorrectly parsed? ** Also affects: xrandr (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1792167 Title: Display size detected incorrectly Status in mutter package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: Invalid Status in xrandr package in Ubuntu: New Bug description: My external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. It seems not related to the display server, compositor or window manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on Wayland). Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-09-05 (372 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: qtbase-opensource-src PackageArchitecture: amd64 Tags: bionic Uname: Linux 4.18.7-041807-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo vboxusers video voice _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788420] Re: Update to 2:10.78.05-0.1
** Bug watch added: Debian Bug tracker #914850 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914850 ** Also affects: netpbm-free (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914850 Importance: Unknown Status: Unknown ** No longer affects: netpbm ** Also affects: netpbm-free (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1634256 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to netpbm-free in Ubuntu. https://bugs.launchpad.net/bugs/1788420 Title: Update to 2:10.78.05-0.1 Status in netpbm-free package in Ubuntu: Triaged Status in netpbm-free package in Debian: Unknown Status in netpbm-free package in Fedora: Unknown Bug description: The new version is in Debian/experimental but has a soname change and require a transition. Unless we find a good reason to want to it now that's probably not for cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/1788420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788420] Re: Update to 2:10.78.05-0.1
** Bug watch added: Red Hat Bugzilla #1634256 https://bugzilla.redhat.com/show_bug.cgi?id=1634256 ** Also affects: netpbm via https://bugzilla.redhat.com/show_bug.cgi?id=1634256 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to netpbm-free in Ubuntu. https://bugs.launchpad.net/bugs/1788420 Title: Update to 2:10.78.05-0.1 Status in NetPBM: Unknown Status in netpbm-free package in Ubuntu: Triaged Bug description: The new version is in Debian/experimental but has a soname change and require a transition. Unless we find a good reason to want to it now that's probably not for cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/netpbm/+bug/1788420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743736] Re: In overview, windows from all workspaces are shown for the second display (when using "Workspaces span displays")
This bug still exists! Using the plugin circumvents the issue though. I am on Ubuntu 18.10 btw. -- 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/1743736 Title: In overview, windows from all workspaces are shown for the second display (when using "Workspaces span displays") Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: I have disabled workspaces on primary display only, and I have enabled workspaces to span displays, in tweak tool. Now things mostly work how I expect. Windows are isolated to the workspace they are and I can move them between displays (monitors). The issue is if I go into an overview mode. Then, for the primary display, I see only windows from my current workspace. But for the secondary display, I see windows from all workspaces being shown in the overview mode. I would expect that only the windows from the current workspace are shown also on the secondary display in the overview mode. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 02:19:13 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-11-20 (57 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) This bug also affects the new LTS release: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 23 15:25:07 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-05-18 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1743736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792167] Re: Display size detected incorrectly
Do you need any additional information? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1792167 Title: Display size detected incorrectly Status in mutter package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Incomplete Bug description: My external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. It seems not related to the display server, compositor or window manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on Wayland). Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-09-05 (372 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: qtbase-opensource-src PackageArchitecture: amd64 Tags: bionic Uname: Linux 4.18.7-041807-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo vboxusers video voice _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792167] Re: Display size detected incorrectly
I booted up a live disk with Ubuntu 17.04 (Unity) and it shows the same behavior. ** Description changed: - Since Ubuntu switched to Gnome, display scaling does not work correctly. - This is because my external monitor is detected as 7" although it is - 32". All applications which use Qt auto scaling have huge controls! + My external monitor is detected as 7" although it is 32". All + applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. + + It seems not related to the display server, compositor or window manager + since the problem appeared in Ubuntu 17.04 (Mir, Unity) as well es 18.04 + (Mutter, Gnome). I tried it with both Wayland and X (on Wayland). Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-09-05 (372 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: qtbase-opensource-src PackageArchitecture: amd64 Tags: bionic Uname: Linux 4.18.7-041807-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo vboxusers video voice _MarkForUpload: True ** Attachment added: "xrandr output for external display on 17.04" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+attachment/5188747/+files/xrandr.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1792167 Title: Display size detected incorrectly Status in mutter package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Incomplete Bug description: My external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. It seems not related to the display server, compositor or window manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on Wayland). Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-09-05 (372 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: qtbase-opensource-src PackageArchitecture: amd64 Tags: bionic Uname: Linux 4.18.7-041807-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo vboxusers video voice _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792167] Re: Display size detected incorrectly
Same result when I connect via DP->HDMI adapter ** Attachment added: "xrandr output for external display on adapter" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+attachment/5188740/+files/xrandr.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1792167 Title: Display size detected incorrectly Status in mutter package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Incomplete Bug description: Since Ubuntu switched to Gnome, display scaling does not work correctly. This is because my external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-09-05 (372 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: qtbase-opensource-src PackageArchitecture: amd64 Tags: bionic Uname: Linux 4.18.7-041807-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo vboxusers video voice _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792167] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1792167/+attachment/5188325/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1792167 Title: Display size detected incorrectly Status in mutter package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Incomplete Bug description: Since Ubuntu switched to Gnome, display scaling does not work correctly. This is because my external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-09-05 (372 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: qtbase-opensource-src PackageArchitecture: amd64 Tags: bionic Uname: Linux 4.18.7-041807-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo vboxusers video voice _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792167] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1792167/+attachment/5188326/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1792167 Title: Display size detected incorrectly Status in mutter package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Incomplete Bug description: Since Ubuntu switched to Gnome, display scaling does not work correctly. This is because my external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-09-05 (372 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: qtbase-opensource-src PackageArchitecture: amd64 Tags: bionic Uname: Linux 4.18.7-041807-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo vboxusers video voice _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792167] Re: Display size detected incorrectly
1. xrandr I generated the output and attached the section for the external display. I guess the first line already shows the problem: HDMI-1 connected 1920x1080+1366+0 (0x8b) normal (normal left inverted right x axis y axis) 160mm x 90mm It includes "160mm x 90mm" which probably translates to 7". 2. apport I generated the requested log. I installed Ubuntu 17.04, upgraded to 17.10 and now upgraded to 18.04. I use the latest kernel from kernel.ubuntu.com. ** Attachment added: "xrandr output for external display" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+attachment/5188367/+files/xrandr.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1792167 Title: Display size detected incorrectly Status in mutter package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Incomplete Bug description: Since Ubuntu switched to Gnome, display scaling does not work correctly. This is because my external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-09-05 (372 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: qtbase-opensource-src PackageArchitecture: amd64 Tags: bionic Uname: Linux 4.18.7-041807-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo vboxusers video voice _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792167] Re: Display size detected incorrectly
apport information ** Tags added: apport-collected bionic ** Description changed: Since Ubuntu switched to Gnome, display scaling does not work correctly. This is because my external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.3 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2017-09-05 (372 days ago) + InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) + Package: qtbase-opensource-src + PackageArchitecture: amd64 + Tags: bionic + Uname: Linux 4.18.7-041807-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo vboxusers video voice + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1792167/+attachment/5188324/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1792167 Title: Display size detected incorrectly Status in mutter package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Incomplete Bug description: Since Ubuntu switched to Gnome, display scaling does not work correctly. This is because my external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-09-05 (372 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: qtbase-opensource-src PackageArchitecture: amd64 Tags: bionic Uname: Linux 4.18.7-041807-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo vboxusers video voice _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792167] Re: Display size detected wrongly
** Also affects: kernel Importance: Undecided Status: New ** Also affects: xorg-server Importance: Undecided Status: New ** Summary changed: - Display size detected wrongly + Display size detected incorrectly -- 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/1792167 Title: Display size detected incorrectly Status in linux: New Status in Qt: New Status in X.Org X server: New Status in gdm package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Bug description: Since Ubuntu switched to Gnome, display scaling does not work correctly. This is because my external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1792167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792167] [NEW] Display size detected wrongly
Public bug reported: Since Ubuntu switched to Gnome, display scaling does not work correctly. This is because my external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! ** Affects: qt Importance: Undecided Status: New ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: vlc (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Gnome Display Settings" https://bugs.launchpad.net/bugs/1792167/+attachment/5188009/+files/Samsung-7-instead-of-32.png ** Also affects: gdm Importance: Undecided Status: New ** Also affects: vlc Importance: Undecided Status: New ** Also affects: vlc (Ubuntu) Importance: Undecided Status: New ** No longer affects: vlc ** Also affects: gdm (Ubuntu) Importance: Undecided Status: New ** No longer affects: gdm ** Also affects: qt Importance: Undecided Status: New -- 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/1792167 Title: Display size detected wrongly Status in Qt: New Status in gdm package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in vlc package in Ubuntu: New Bug description: Since Ubuntu switched to Gnome, display scaling does not work correctly. This is because my external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1792167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774081] [NEW] /etc/gdm3/Init/Default not evaluated
Public bug reported: /etc/gdm3/Init/Default is not evaluated on my fresh install of Ubuntu 18.04 (minimal). I replaced this file by one with the following content to test it: #!/bin/sh touch /tmp/a touch /mnt/a After a reboot, these files are not available. When I use the same file for /etc/gdm3/PostLogin/Default, it works. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1774081 Title: /etc/gdm3/Init/Default not evaluated Status in gdm3 package in Ubuntu: New Bug description: /etc/gdm3/Init/Default is not evaluated on my fresh install of Ubuntu 18.04 (minimal). I replaced this file by one with the following content to test it: #!/bin/sh touch /tmp/a touch /mnt/a After a reboot, these files are not available. When I use the same file for /etc/gdm3/PostLogin/Default, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763488] [NEW] restore only does not use information from "folder" text field
Public bug reported: I want to restore files from a server backup. I do not want to create a backup. So I click in the "Overview" tab the "Restore" button and then select my Nextcloud server and enter something in the "Folder" field. This does not work When I enter the information in "Storage location" and then start the restore, it works. When I click again on "Restore" and change the information in the "Folder" field, it still uses the old folder (the one in "Storage location"). So my conclusion is that the "Folder" field in the "Restore" dialog is just ignored and the information from "Storage location" is used instead. Can someone confirm? ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1763488 Title: restore only does not use information from "folder" text field Status in deja-dup package in Ubuntu: New Bug description: I want to restore files from a server backup. I do not want to create a backup. So I click in the "Overview" tab the "Restore" button and then select my Nextcloud server and enter something in the "Folder" field. This does not work When I enter the information in "Storage location" and then start the restore, it works. When I click again on "Restore" and change the information in the "Folder" field, it still uses the old folder (the one in "Storage location"). So my conclusion is that the "Folder" field in the "Restore" dialog is just ignored and the information from "Storage location" is used instead. Can someone confirm? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1763488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 270479] Re: Debian/Ubuntu netpbm is many years out-of-date with upstream
Surprisingly, ppmtompeg is *not* removed in the updated Debian package... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to netpbm-free in Ubuntu. https://bugs.launchpad.net/bugs/270479 Title: Debian/Ubuntu netpbm is many years out-of-date with upstream Status in netpbm-free package in Ubuntu: Confirmed Status in netpbm-free package in Debian: Fix Released Bug description: I'm having a little trouble following the difference between netpbm- free and the upstream version of netpbm available at http://netpbm.sourceforge.net, so I'm not sure if the version numbers are comparable, but it appears that the netpbm-free package is woefully out of date with upstream. I'm trying to use the -data option of pnmmontage which is was introduced into (upstream) version 10.06 of pnmmontage in 2002 (see http://netpbm.svn.sourceforge.net/viewvc/netpbm/stable/doc/HISTORY?view=markup). While I'm not sure if the version numbers can be compared easily, it appears that Ubuntu is at 10.0 while the upstream netpbm libraries are at 10.35.51, which is 6 years covering 40 or so releases ahead of Ubuntu/Debian's version. What can be done to bring Ubuntu (and Debian) back up to date with the upstream versions of netpbm? Are there some licensing issues that are holding the repackaging up? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/270479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 270479] Re: Debian/Ubuntu netpbm is many years out-of-date with upstream
This is also stated in their source preparation script: "removing the ppmtompeg code, due to patents" (http://pkgs.fedoraproject.org/cgit/rpms/netpbm.git/tree/netpbm2tar.sh). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to netpbm-free in Ubuntu. https://bugs.launchpad.net/bugs/270479 Title: Debian/Ubuntu netpbm is many years out-of-date with upstream Status in netpbm-free package in Ubuntu: Confirmed Status in netpbm-free package in Debian: Fix Released Bug description: I'm having a little trouble following the difference between netpbm- free and the upstream version of netpbm available at http://netpbm.sourceforge.net, so I'm not sure if the version numbers are comparable, but it appears that the netpbm-free package is woefully out of date with upstream. I'm trying to use the -data option of pnmmontage which is was introduced into (upstream) version 10.06 of pnmmontage in 2002 (see http://netpbm.svn.sourceforge.net/viewvc/netpbm/stable/doc/HISTORY?view=markup). While I'm not sure if the version numbers can be compared easily, it appears that Ubuntu is at 10.0 while the upstream netpbm libraries are at 10.35.51, which is 6 years covering 40 or so releases ahead of Ubuntu/Debian's version. What can be done to bring Ubuntu (and Debian) back up to date with the upstream versions of netpbm? Are there some licensing issues that are holding the repackaging up? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/270479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 270479] Re: Debian/Ubuntu netpbm is many years out-of-date with upstream
I noticed that Fedora is removing "ppmtompeg". So I guess this is the "solution" to the license problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to netpbm-free in Ubuntu. https://bugs.launchpad.net/bugs/270479 Title: Debian/Ubuntu netpbm is many years out-of-date with upstream Status in netpbm-free package in Ubuntu: Confirmed Status in netpbm-free package in Debian: Fix Released Bug description: I'm having a little trouble following the difference between netpbm- free and the upstream version of netpbm available at http://netpbm.sourceforge.net, so I'm not sure if the version numbers are comparable, but it appears that the netpbm-free package is woefully out of date with upstream. I'm trying to use the -data option of pnmmontage which is was introduced into (upstream) version 10.06 of pnmmontage in 2002 (see http://netpbm.svn.sourceforge.net/viewvc/netpbm/stable/doc/HISTORY?view=markup). While I'm not sure if the version numbers can be compared easily, it appears that Ubuntu is at 10.0 while the upstream netpbm libraries are at 10.35.51, which is 6 years covering 40 or so releases ahead of Ubuntu/Debian's version. What can be done to bring Ubuntu (and Debian) back up to date with the upstream versions of netpbm? Are there some licensing issues that are holding the repackaging up? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netpbm-free/+bug/270479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1388577] Re: xrandr --rotate rotates only lower half the screen
I made an extra bug for the inverted mouse pointer (please also confirm there): https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1388596 But as you have the same problems, maybe these two bugs are related? ** Description changed: When I run xrandr --output LVDS1 --rotate inverted while I am in the state normal, it rotates only lower half of the screen (see attached screenshot). This is only the case from normal to inverted. All other combinations work as intended. - I use Ubuntu 14.10 with intel graphics card. + I use Ubuntu 14.10 with intel graphics card (Lenovo Twist S230u). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1388577 Title: xrandr --rotate rotates only lower half the screen Status in “xorg-server” package in Ubuntu: Confirmed Bug description: When I run xrandr --output LVDS1 --rotate inverted while I am in the state normal, it rotates only lower half of the screen (see attached screenshot). This is only the case from normal to inverted. All other combinations work as intended. I use Ubuntu 14.10 with intel graphics card (Lenovo Twist S230u). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1388577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1388577] Re: xrandr --rotate rotates only lower half the screen
You use the Yoga which is quite similar to the Twist I am using. Maybe the bug has to do something with the drivers then? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1388577 Title: xrandr --rotate rotates only lower half the screen Status in “xorg-server” package in Ubuntu: Confirmed Bug description: When I run xrandr --output LVDS1 --rotate inverted while I am in the state normal, it rotates only lower half of the screen (see attached screenshot). This is only the case from normal to inverted. All other combinations work as intended. I use Ubuntu 14.10 with intel graphics card (Lenovo Twist S230u). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1388577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1388577] [NEW] xrandr --rotate rotates only lower half the screen
Public bug reported: When I run xrandr --output LVDS1 --rotate inverted while I am in the state normal, it rotates only lower half of the screen (see attached screenshot). This is only the case from normal to inverted. All other combinations work as intended. I use Ubuntu 14.10 with intel graphics card. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Attachment added: Screenshot https://bugs.launchpad.net/bugs/1388577/+attachment/4251372/+files/Screenshot%20from%202014-11-02%2015%3A33%3A16.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1388577 Title: xrandr --rotate rotates only lower half the screen Status in “xorg-server” package in Ubuntu: New Bug description: When I run xrandr --output LVDS1 --rotate inverted while I am in the state normal, it rotates only lower half of the screen (see attached screenshot). This is only the case from normal to inverted. All other combinations work as intended. I use Ubuntu 14.10 with intel graphics card. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1388577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1388596] [NEW] xrandr --rotate duplicates mouse curser
Public bug reported: When I ran xrandr --output LVDS1 --rotate normal from any other orientation, then the previous mouse pointer (icon) is duplicated a few pixel below the current mouse pointer. I am using Ubuntu 14.10. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1388596 Title: xrandr --rotate duplicates mouse curser Status in “xorg-server” package in Ubuntu: New Bug description: When I ran xrandr --output LVDS1 --rotate normal from any other orientation, then the previous mouse pointer (icon) is duplicated a few pixel below the current mouse pointer. I am using Ubuntu 14.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1388596/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
