[Bug 1767654] Re: Cursor gets stuck on left side of the screen
If you have any Gnome Shell extensions installed, please try disabling them and tell us if that fixes the problem. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: Cursor gets stuck on left side of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767654/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767342] Re: Dosplay scale factor reset after changing screen size or reboot
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: hidpi -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1767342 Title: Dosplay scale factor reset after changing screen size or reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767342/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797301] Re: Keyboard input stops being processed entirely
Suggestions: 1. Disable all extensions and tell us if the problem then goes away: b'org.gnome.shell' b'enabled-extensions' b"['foo', 'hams...@projecthamster.wordpress.com', 'gTile@vibou']" 2. Try logging in to "Ubuntu on Wayland" tell us if that avoids the problem. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797301 Title: Keyboard input stops being processed entirely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767342] [NEW] Dosplay scale factor reset after changing screen size or reboot
You have been subscribed to a public bug: Steps to reproduce 1. Take computer with HiDPI monitor 2. Install bionic in VM, install open-vm-tools && open-vm-tools-desktop and enable hi-dpi 3. Settings-Devices-Display-Scale to 200% and press apply 4. Drag VM window corner for changing VM screen size or simple reboot VM. Scale resets to 100% ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Fri Apr 27 14:20:34 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=203b7377-6f0c-4d39-a33f-db18baece74c ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2017 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- Dosplay scale factor reset after changing screen size or reboot https://bugs.launchpad.net/bugs/1767342 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797301] [NEW] Keyboard input stops being processed entirely
Public bug reported: >From time-to-time, when using cosmic, my keyboard presses will no longer register. This applies to both the internal laptop keyboard and my external keyboard. I haven't identified any particular trigger of this. The one workaround I have found is to use the mouse (which is still fully functional, along with everything else about my desktop environment except keyboard input) to click the "Show Applications" button; this appeared to free up my keyboard input. (The lock-up has happened multiple times, but it only just occurred to me to attempt that as a work-around; this may not be reliable.) My keyboards did continue to work perfectly fine in a serial console, but switching to/from the console did not unlock input in GNOME Shell. Nor did unplugging and replugging my external keyboard. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 11 00:23:08 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-23 (352 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-09-10 (30 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797301 Title: Keyboard input stops being processed entirely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797301] Re: Keyboard input stops being processed entirely
Is there anything specific that I can do to capture more information when this happens again? Browsing through the systemd journal didn't reveal anything obvious, but I don't necessarily know what to look for. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797301 Title: Keyboard input stops being processed entirely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797301/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1745888 Title: Two instances of a program launch whenever you touch a favorites icon To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797198] Re: [nvidia] After login the screen goes black
It appears the main error here is: (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission. which may related to bug 1795637, but probably not. It sounds like a similar problem but in this case the bug would be in gdm3 instead of plymouth. As a workaround you might want to try disabling KMS and let the Nvidia driver operate natively. To do this, 1. Edit /etc/default/grub and add "nomodeset": GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" 2. sudo update-grub 3. Reboot That does roughly the same thing as the recovery mode workaround. ** Package changed: gnome-shell (Ubuntu) => xorg-server (Ubuntu) ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1797198 Title: [nvidia] After login the screen goes black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1797198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1698573] Re: Screen rotation no longer works with 17.04
Thank you for reporting this bug to Ubuntu. Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed. ** Changed in: iio-sensor-proxy (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1698573 Title: Screen rotation no longer works with 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1698573/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797198] Re: After login the screen goes black
** Summary changed: - Oct 10 18:22:28 pi-GA-990FXA-UD3 /usr/lib/gdm3/gdm-x-session[1676]: Fatal server error: + After login the screen goes black ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags added: black-screen nvidia ** Summary changed: - After login the screen goes black + [nvidia] After login the screen goes black -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1797198 Title: [nvidia] After login the screen goes black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1797198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767650] Re: [HP Elitebook Folio 9470m] Screen rotates upside-down when laptop is not flat
** Summary changed: - Screen rotates upside-down when laptop is not flat + [HP Elitebook Folio 9470m] Screen rotates upside-down when laptop is not flat -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1767650 Title: [HP Elitebook Folio 9470m] Screen rotates upside-down when laptop is not flat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1767650/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797178] Re: gnome-shell activities / application icon touches not fully registering
Please start by disabling your extensions: b'org.gnome.shell' b'enabled-extensions' b"['bettervol...@tudmotu.com', 'native-window-placem...@gnome-shell-extensions.gcampax.github.com', 'caffe...@patapon.info', 'newinstancewithwheelbut...@creak.foolstep.com', 'audio-output- switcher@anduchs', 'audio-input-switcher@anduchs']" and verify the bug still occurs without them. ** Tags added: touch ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797178 Title: gnome-shell activities / application icon touches not fully registering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797174] Re: gnome-shell unrotates immediately after rotating
** Also affects: iio-sensor-proxy (Ubuntu) Importance: Undecided Status: New ** Summary changed: - gnome-shell unrotates immediately after rotating + [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1797174 Title: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797141] Re: gnome-shell frequent restart or crash after unlocking screen or resume from sleep
1. Please disable your extensions as we find a large number of crashes are caused by gnome-shell extensions. And you have a lot of them: b'org.gnome.shell' b'enabled-extensions' b"['center-area-horizontal- spacing@kirby...@hotmail.fr', 'dash-to-d...@micxgx.gmail.com', 'mediapla...@patapon.info', 'remove-dropdown-arr...@mpdeimos.com', 'status-area-horizontal-spac...@mathematical.coffee.gmail.com', 'transparentnotification@ipaq3870', 'user-theme@gnome-shell- extensions.gcampax.github.com', 'apps-menu@gnome-shell- extensions.gcampax.github.com', 'aws_ec2_conn...@msoute.gmail.com', 'ar...@pew.worldwidemann.com', 'caffe...@patapon.info', 'clipboard- indica...@tudmotu.com', 'docker_status@gpouilloux', 'easyscreenc...@iacopodeenosee.gmail.com', 'appindicatorsupp...@rgcjonas.gmail.com', 'openweather- extens...@jenslody.de', 'todo@bart.libert.gmail.com', 'window- corner-prev...@fabiomereu.it', 'freon@UshakovVasilii_Github.yahoo.com', 'native-window-placem...@gnome-shell-extensions.gcampax.github.com', 'timepp@zagortenay333', 'coverflowalt...@palatis.blogspot.com']" 2. Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797141 Title: gnome-shell frequent restart or crash after unlocking screen or resume from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797141/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747566] Re: syslog fills with messages: Object ..., has been already finalized. Impossible to get any property from it. ... (stack trace in tweener.js)
This bug is closed. If you find any problem in gnome-shell without extensions loaded then please open a new bug. As for figuring out which extensions are to blame, that's an exercise for the reader, sorry. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1747566 Title: syslog fills with messages: Object ..., has been already finalized. Impossible to get any property from it. ... (stack trace in tweener.js) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1747566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797275] [NEW] libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent.
Public bug reported: The binary "gtk-query-immodules-3.0" is absent from package. The package DOES include the man-page for "gtk-query-immodules-3.0", but not the actual utility it documents. I downloaded the source tarball "gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz" and untar-ed it: |$ ls ./ |debian |gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz |$ ls ./debian/libgtk-3-bin* |debian/libgtk-3-bin.install |debian/libgtk-3-bin.links.in |$ cat ./debian/libgtk-3-bin.install |usr/bin/broadwayd |usr/bin/gtk-builder-tool |usr/bin/gtk-launch |usr/bin/gtk-query-settings |usr/share/gettext/its/gtkbuilder.its |usr/share/gettext/its/gtkbuilder.loc |usr/share/man/man1/broadwayd.1 |usr/share/man/man1/gtk-builder-tool.1 |usr/share/man/man1/gtk-launch.1 |usr/share/man/man1/gtk-query-immodules-3.0.1 |usr/share/man/man1/gtk-query-settings.1 Qualifiers: 1) |$ lsb_release -rd |Description: Linux Mint 19 Tara |Release: 19 2) |$ apt-cache policy libgtk-3-bin |libgtk-3-bin: | Installed: 3.22.30-1ubuntu1 | Candidate: 3.22.30-1ubuntu1 | Version table: | *** 3.22.30-1ubuntu1 500 |500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages |100 /var/lib/dpkg/status |$ ls /usr/share/man/man1/gtk-query* |/usr/share/man/man1/gtk-query-immodules-2.0.1.gz |/usr/share/man/man1/gtk-query-immodules-3.0.1.gz |/usr/share/man/man1/gtk-query-settings.1.gz |$ ls /usr/bin/gtk-query* |/usr/bin/gtk-query-settings 3) I am experimenting with development of specialized immodules for GtkEntry widget. I expect to be able to install these additional modules and for my application to access them per the instructions in the Gtk+3 documentation. 4) |$ whereis gtk-query-immodules-3.0 |gtk-query-immodules-3: Thank you! ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: gtk-query-immodules-3.0 immodule libgtk-3-bin -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1797275 Title: libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1797275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796872] Re: /usr/bin/gnome-control-center:11:g_type_check_instance_cast:whoopsie_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic
This bug was fixed in the package gnome-control-center - 1:3.30.1-1ubuntu2 --- gnome-control-center (1:3.30.1-1ubuntu2) cosmic; urgency=medium * d/p/region-Fix-double-free-when-closing-the-input-chooser-dia.patch: - Cherry pick upstream segfault fix for the region settings [ Andrea Azzarone ] * d/p/privacy-panel-whoopsie.patch: Unref the whoopsie proxy (LP: #1796872) -- Sebastien Bacher Wed, 10 Oct 2018 16:28:01 +0200 ** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1796872 Title: /usr/bin/gnome-control- center:11:g_type_check_instance_cast:whoopsie_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1796872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1756826] Re: hangs when remote search provider performs expensive operation
** Changed in: gnome-software (Ubuntu) Assignee: Andrea Azzarone (azzar1) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1756826 Title: hangs when remote search provider performs expensive operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1756826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797254] [NEW] Update epiphany to 3.30.1
Public bug reported: https://gitlab.gnome.org/GNOME/epiphany/blob/gnome-3-30/NEWS https://gitlab.gnome.org/GNOME/epiphany/compare/3.30.0...3.30.1 ** Affects: epiphany-browser (Ubuntu) Importance: Medium Status: In Progress ** Tags: cosmic upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1797254 Title: Update epiphany to 3.30.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1797254/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797236] [NEW] network-manager openvpn settings not being saved
Public bug reported: I'm seeing some weird issue with the new NM + openvpn; if I create a new VPN connection, and add certificate options (verify name exactly, plus TLS auth), these options are not saved, leading to the connection failing. The following versions lead to an invalid connection: ii network-manager 1.12.4-1ubuntu1 amd64 network management framework (daemon and userspace tools) ii network-manager-openvpn 1.8.6-1 amd64 network management framework (OpenVPN plugin core) Reverting to the following versions, things work again: ii network-manager 1.12.2-0ubuntu4 amd64 network management framework (daemon and userspace tools) ii network-manager-openvpn 1.8.4-1 amd64 network management framework (OpenVPN plugin core) If I use an existing connection saved with a prior version of NM, the connection will be successful. If I go open the settings, hit Apply, all advanced TLS settings are wiped. The connection then fails: Oct 10 16:58:52 demeter nm-openvpn[6538]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Oct 10 16:58:52 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used remote address: [AF_INET]91.189.91.19:443 Oct 10 16:58:52 demeter nm-openvpn[6538]: Attempting to establish TCP connection with [AF_INET]91.189.91.19:443 [nonblock] Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP connection established with [AF_INET]91.189.91.19:443 Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link local: (not bound) Oct 10 16:58:53 demeter nm-openvpn[6538]: TCP_CLIENT link remote: [AF_INET]xx.xx.xx.xx:443 Oct 10 16:58:53 demeter nm-openvpn[6538]: Connection reset, restarting [0] Oct 10 16:58:53 demeter nm-openvpn[6538]: SIGUSR1[soft,connection-reset] received, process restarting Oct 10 16:58:58 demeter nm-openvpn[6538]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. Oct 10 16:58:58 demeter nm-openvpn[6538]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Oct 10 16:58:58 demeter nm-openvpn[6538]: TCP/UDP: Preserving recently used remote address: [AF_INET6]2001:67c:1562:0:1::1:443 Oct 10 16:58:58 demeter nm-openvpn[6538]: Attempting to establish TCP connection with [AF_INET6]2001:67c:1562:0:1::1:443 [nonblock] Oct 10 16:58:59 demeter nm-openvpn[6538]: TCP: connect to [AF_INET6]:xxx:xx:xx::xx:443 failed: Network is unreachable Oct 10 16:58:59 demeter nm-openvpn[6538]: SIGUSR1[connection failed(soft),init_instance] received, process restarting Oct 10 16:59:04 demeter nm-openvpn[6538]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1797236 Title: network-manager openvpn settings not being saved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1797236/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795637] Re: No login screen when booting Cosmic
I've uploaded a pkg to cosmic unapproved which contains https://gitlab.freedesktop.org/plymouth/plymouth/commit/85d843af843589ce8538a59e5cb665b8253e380d amongst a few other cherry picks that are worthwhile to have in cosmic. --- details unrelated to this bug (boot race with plymouth & DRM) --- I know this isn't the end of the story with regard to boot races (there's a "Could not find primary drm kms device" thing that Trevinho is looking into), but it gets us closer. Possibly we should use a new bug for that other problem so this one doesn't get confusing with multiple fixes for a broad symptom. (If so, please file it, rls nominate it, attach the journal logs that show the bug happening so it's clear it's about that problem and no other and assign to Trevinho) ** Summary changed: - No login screen when booting Cosmic + No login screen when booting Cosmic due to plymouth racing with the rest of the boot process and not releasing DRM devices in time ** Changed in: gdm3 (Ubuntu Cosmic) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1795637 Title: No login screen when booting Cosmic due to plymouth racing with the rest of the boot process and not releasing DRM devices in time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1795637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797224] [NEW] Stay on 2.0 for cosmic, update next cycle
Public bug reported: The new version requires the MIR situation to be sorted out ** Affects: tracker (Ubuntu) Importance: Wishlist Status: Triaged ** Tags: upgrade-software-version version-blocked-ff ** Changed in: tracker (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1797224 Title: Stay on 2.0 for cosmic, update next cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1797224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797190] Re: It can not be formatted with 'gnome-disk-utility 3.30.1' the pendrive
** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1797190 Title: It can not be formatted with 'gnome-disk-utility 3.30.1' the pendrive To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1797190/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797205] Re: /usr/bin/gnome-control-center:11:g_type_check_instance:g_signal_handlers_block_matched:als_enabled_state_changed:ffi_call_unix64:ffi_call
MP Upstream: https://gitlab.gnome.org/GNOME/gnome-control- center/merge_requests/234 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1797205 Title: /usr/bin/gnome-control- center:11:g_type_check_instance:g_signal_handlers_block_matched:als_enabled_state_changed:ffi_call_unix64:ffi_call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1797205/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797205] [NEW] /usr/bin/gnome-control-center:11:g_type_check_instance:g_signal_handlers_block_matched:als_enabled_state_changed:ffi_call_unix64:ffi_call
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/2ddf38bad57fd999c49468a7407614123cac3e11 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-control-center (Ubuntu) Importance: High Assignee: Andrea Azzarone (azzar1) Status: In Progress ** Tags: cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1797205 Title: /usr/bin/gnome-control- center:11:g_type_check_instance:g_signal_handlers_block_matched:als_enabled_state_changed:ffi_call_unix64:ffi_call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1797205/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797205] Re: /usr/bin/gnome-control-center:11:g_type_check_instance:g_signal_handlers_block_matched:als_enabled_state_changed:ffi_call_unix64:ffi_call
** Changed in: gnome-control-center (Ubuntu) Status: New => In Progress ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: gnome-control-center (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1797205 Title: /usr/bin/gnome-control- center:11:g_type_check_instance:g_signal_handlers_block_matched:als_enabled_state_changed:ffi_call_unix64:ffi_call To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1797205/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797190] Re: It can not be formatted with 'gnome-disk-utility' the pendrive
** Description changed: + List: linux-usb + https://marc.info/?l=linux-usb=153919676204905=2 + + --- + https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/104 --- Hello, I am trying to format a pendrive of 2TB(Purchased in China for ebay). What I do is the following: 1) I start the notebook with Linux 4.18.0-9 2) I start with my GNOME session 3) I connect the pendrive 4) I open Nautilus 5) The pendrive in nautilus appears as mounted 6) In nautilus I hit a right click with the mouse to my pedrive 7) I choose 'Format' 8) A window opens where I can only choose between: ext4, NTFS or FAT 9) I leave the default -> 'NTFS' 10) Next press 11) I change to the next window where the information of what is going to happen appears and I confirm the format 12) Then I return to nautilius 13) The pendrive appears in nautilus 14) It can not be accessed, even though the pendrive is mounted Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2162 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 14:30:28 2018 InstallationDate: Installed on 2017-10-13 (362 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Summary changed: - It can not be formatted with 'gnome-disk-utility' the pendrive + It can not be formatted with 'gnome-disk-utility 3.30.1' the pendrive -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1797190 Title: It can not be formatted with 'gnome-disk-utility 3.30.1' the pendrive To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1797190/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797190] Re: It can not be formatted with 'gnome-disk-utility' the pendrive
https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/104 -- Cristian Aravena Romero (caravena) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1797190 Title: It can not be formatted with 'gnome-disk-utility' the pendrive To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1797190/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797190] Re: It can not be formatted with 'gnome-disk-utility' the pendrive
** Description changed: https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/104 --- Hello, - I am trying to format a pendrive 2TB(Purchased in China for ebay). What - I do is the following: + I am trying to format a pendrive of 2TB(Purchased in China for ebay). + What I do is the following: 1) I start the notebook with Linux 4.18.0-9 2) I start with my GNOME session 3) I connect the pendrive 4) I open Nautilus 5) The pendrive in nautilus appears as mounted 6) In nautilus I hit a right click with the mouse to my pedrive 7) I choose 'Format' 8) A window opens where I can only choose between: ext4, NTFS or FAT 9) I leave the default -> 'NTFS' 10) Next press 11) I change to the next window where the information of what is going to happen appears and I confirm the format 12) Then I return to nautilius 13) The pendrive appears in nautilus 14) It can not be accessed, even though the pendrive is mounted Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2162 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 14:30:28 2018 InstallationDate: Installed on 2017-10-13 (362 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Bug watch added: Linux Kernel Bug Tracker #201371 https://bugzilla.kernel.org/show_bug.cgi?id=201371 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=201371 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1797190 Title: It can not be formatted with 'gnome-disk-utility' the pendrive To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1797190/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797190] Re: It can not be formatted with 'gnome-disk-utility' the pendrive
** Attachment added: "dmesg_4.19.0-041900rc7-generic.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797190/+attachment/5199640/+files/dmesg_4.19.0-041900rc7-generic.txt ** Description changed: Hello, - I am trying to format a pendrive. What I do is the following: + I am trying to format a pendrive 2TB(purchased in China). What I do is + the following: 1) I start the notebook with Linux 4.18.0-9 2) I start with my GNOME session 3) I connect the pendrive 4) I open Nautilus 5) The pendrive in nautilus appears as mounted 6) In nautilus I hit a right click with the mouse to my pedrive 7) I choose 'Format' 8) A window opens where I can only choose between: ext4, NTFS or FAT 9) I leave the default -> 'NTFS' 10) Next press 11) I change to the next window where the information of what is going to happen appears and I confirm the format 12) Then I return to nautilius 13) The pendrive appears in nautilus 14) It can not be accessed, even though the pendrive is mounted Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2162 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 14:30:28 2018 InstallationDate: Installed on 2017-10-13 (362 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Description changed: Hello, - I am trying to format a pendrive 2TB(purchased in China). What I do is - the following: + I am trying to format a pendrive 2TB(purchased in China for ebay). What + I do is the following: 1) I start the notebook with Linux 4.18.0-9 2) I start with my GNOME session 3) I connect the pendrive 4) I open Nautilus 5) The pendrive in nautilus appears as mounted 6) In nautilus I hit a right click with the mouse to my pedrive 7) I choose 'Format' 8) A window opens where I can only choose between: ext4, NTFS or FAT 9) I leave the default -> 'NTFS' 10) Next press 11) I change to the next window where the information of what is going to happen appears and I confirm the format 12) Then I return to nautilius 13) The pendrive appears in nautilus 14) It can not be accessed, even though the pendrive is mounted Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2162 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 14:30:28 2018 InstallationDate: Installed on 2017-10-13 (362 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install)
[Bug 1797198] [NEW] Oct 10 18:22:28 pi-GA-990FXA-UD3 /usr/lib/gdm3/gdm-x-session[1676]: Fatal server error:
Public bug reported: When I boot Cosmic, grub is working OK and login screen is presented OK, but after login the screen goes black. When I boot in Recovery Mode" and "Resume" all is working OK and Nvidia driver 390 is used. These bugs my be related https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1770238 https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1748656 https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192 See attachment for syslog info. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 20:12:32 2018 InstallationDate: Installed on 2018-10-10 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181010.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Attachment added: "nvidia-problem-3" https://bugs.launchpad.net/bugs/1797198/+attachment/5199647/+files/nvidia-problem-3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1797198 Title: Oct 10 18:22:28 pi-GA-990FXA-UD3 /usr/lib/gdm3/gdm-x-session[1676]: Fatal server error: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1797198/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797190] Re: It can not be formatted with 'gnome-disk-utility' to pendrive
** Description changed: Hello, I am trying to format a pendrive. What I do is the following: 1) I start the notebook with Linux 4.18.0-9 - 2) Join my GNOME session + 2) I start with my GNOME session 3) I connect the pendrive 4) I open Nautilus 5) The pendrive in nautilus appears as mounted 6) In nautilus I hit a right click with the mouse to my pedrive 7) I choose 'Format' 8) A window opens where I can only choose between: ext4, NTFS or FAT 9) I leave the default -> 'NTFS' 10) Next press 11) I change to the next window where the information of what is going to happen appears and I confirm the format 12) Then I return to nautilius 13) The pendrive appears in nautilus 14) It can not be entered, even though the pendrive is mounted Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2162 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 14:30:28 2018 InstallationDate: Installed on 2017-10-13 (362 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Description changed: Hello, I am trying to format a pendrive. What I do is the following: 1) I start the notebook with Linux 4.18.0-9 2) I start with my GNOME session 3) I connect the pendrive 4) I open Nautilus 5) The pendrive in nautilus appears as mounted 6) In nautilus I hit a right click with the mouse to my pedrive 7) I choose 'Format' 8) A window opens where I can only choose between: ext4, NTFS or FAT 9) I leave the default -> 'NTFS' 10) Next press 11) I change to the next window where the information of what is going to happen appears and I confirm the format 12) Then I return to nautilius 13) The pendrive appears in nautilus - 14) It can not be entered, even though the pendrive is mounted + 14) It can not be accessed, even though the unit is mounted Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2162 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 14:30:28 2018 InstallationDate: Installed on 2017-10-13 (362 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9
[Bug 1797190] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1797190 Title: It can not be formatted with 'gnome-disk-utility' to pendrive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1797190/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797190] [NEW] It can not be formatted with 'gnome-disk-utility' to pendrive
Public bug reported: Hello, I am trying to format a pendrive. What I do is the following: 1) I start the notebook with Linux 4.18.0-9 2) I start with my GNOME session 3) I connect the pendrive 4) I open Nautilus 5) The pendrive in nautilus appears as mounted 6) In nautilus I hit a right click with the mouse to my pedrive 7) I choose 'Format' 8) A window opens where I can only choose between: ext4, NTFS or FAT 9) I leave the default -> 'NTFS' 10) Next press 11) I change to the next window where the information of what is going to happen appears and I confirm the format 12) Then I return to nautilius 13) The pendrive appears in nautilus 14) It can not be accessed, even though the pendrive is mounted Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2162 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 14:30:28 2018 InstallationDate: Installed on 2017-10-13 (362 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug cosmic package-from-proposed wayland-session ** Summary changed: - It can not be formatted with 'gnome-disk-utility 3.30.1' and access with 'nautilus 3.26.4' to pendrive + It can not be formatted with 'gnome-disk-utility' and access with 'nautilus' to pendrive ** Also affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Summary changed: - It can not be formatted with 'gnome-disk-utility' and access with 'nautilus' to pendrive + It can not be formatted with 'gnome-disk-utility' to pendrive ** Description changed: Hello, I am trying to format a pendrive. What I do is the following: 1) I start the notebook with Linux 4.18.0-9 2) Join my GNOME session 3) I connect the pendrive 4) I open Nautilus 5) The pendrive in nautilus appears as mounted 6) In nautilus I hit a right click with the mouse to my pedrive 7) I choose 'Format' 8) A window opens where I can only choose between: ext4, NTFS or FAT 9) I leave the default -> 'NTFS' 10) Next press 11) I change to the next window where the information of what is going to happen appears and I confirm the format 12) Then I return to nautilius 13) The pendrive appears in nautilus - 14) It can not be entered, even though the unit is mounted + 14) It can not be entered, even though the pendrive is mounted Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: caravena 2162 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: caravena 2162 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 14:30:28 2018 InstallationDate: Installed on 2017-10-13 (362 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-9-generic
[Bug 1574614] Re: Losing focus when trying to rename file or folder
I also have the same issue with nautilus in Ubuntu 16.10. It affects only the list view, grid view works fine. Also other file browsers like Thunar work fine in both list and grid view. Additional notes: - Pressing Ctrl seems to switch off the editing mode. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1574614 Title: Losing focus when trying to rename file or folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1574614/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796554] Re: seahorse crashed with SIGSEGV in g_variant_unref()
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1796554 Title: seahorse crashed with SIGSEGV in g_variant_unref() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1796554/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797172] Re: gjs-console crashed with SIGABRT
*** This bug is a duplicate of bug 1796649 *** https://bugs.launchpad.net/bugs/1796649 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1796649, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1797172/+attachment/5199561/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1797172/+attachment/5199563/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1797172/+attachment/5199567/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1797172/+attachment/5199568/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1797172/+attachment/5199569/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1797172/+attachment/5199570/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1797172/+attachment/5199571/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1796649 gjs-console crashed with SIGABRT in g_assertion_message() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1797172 Title: gjs-console crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1797172/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797178] [NEW] gnome-shell activities / application icon touches not fully registering
Public bug reported: On a dell xps 15 2-in-1 (model 9575), the touchscreen mostly works. However, in gnome-shell, touching the top-left 'Activities' menu results in a quick flash of the menu button, but not the launching of the overview. Once in the overview (via mouse/keyboard/swipe-from-left), touching on an application icon (in either the left tray or the applications grid) results in the application icon flashing, but not activating. A long-touch will bring up a menu in which touching on "new window" works properly. Additionally, touching the "show applications" grid button works, as do other components of the top bar, its only the the "activities" menu button and app icon launchers that are "registering" a touch but not activating properly. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 10 09:13:40 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-26 (14 days ago) InstallationMedia: 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: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-09-28 (11 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797178 Title: gnome-shell activities / application icon touches not fully registering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797174] Re: gnome-shell unrotates immediately after rotating
** Summary changed: - gnome-shell unrotates immeditely after rotating + gnome-shell unrotates immediately after rotating -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797174 Title: gnome-shell unrotates immediately after rotating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726516] Re: no progress bar while copying files
This is still happening. Ubuntu Budgie 18.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1726516 Title: no progress bar while copying files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797174] [NEW] gnome-shell unrotates immediately after rotating
Public bug reported: on a dell xps 15 2-in-1 (model 9575), I've enabled iio-sensor-proxy functionality by doing: modprobe intel-ish-ipc echo "8086 a135" > /sys/bus/pci/drivers/intel_ish_ipc/new_id This makes `monitor-sensor` display rotation events, and gnome-shell auto-rotate the screen upon receiving them. However, immediately after rotating, the screen rotates back to its normal orientation (unless I quickly lock rotation), displaying the following in journalctl: Oct 10 09:06:19 taplop gnome-shell[2616]: Failed to apply DRM plane transform 1: Invalid argument Oct 10 09:06:20 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Oct 10 09:06:20 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Oct 10 09:06:20 taplop kernel: [drm] VCE initialized successfully. Oct 10 09:06:27 taplop kernel: amdgpu :01:00.0: GPU pci config reset ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 10 09:06:40 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-26 (14 days ago) InstallationMedia: 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: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-09-28 (11 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797174 Title: gnome-shell unrotates immediately after rotating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1747566] Re: syslog fills with messages: Object ..., has been already finalized. Impossible to get any property from it. ... (stack trace in tweener.js)
I had this "large log file" issue with gnome-shell for a long time (1-2
years). Only drawback was, I was not being able to send crash reports to
launchpad after gnome-shell crashes (which are more frequent than
expected)
But recently, after apt update; apt upgrade, couple months ago, gnome-
shell became very unstable. Right now, after each screen lock or resume
it restarts and occasionally Xorg crashes right after putting in the
password. I file a bug about this instability
(https://bugs.launchpad.net/gnome-shell/+bug/1797141).
Long story short, I have gnome-shell version 3.28.3-0ubuntu0.18.04.2 and
still has the large log file problem.
Here's the count of lines in logs:
$ journalctl | cut -f3 -d: | cut -f3 -d" " | sed -e 's/[0-9]//g' | awk
'{proc[$1]++}END{ for (i in proc) print i,proc[i] | "sort -k2nr"}'
org.gnome.Shell.desktop[] 2579197
albert.desktop[] 824603
gnome-shell[] 328024
/usr/lib/gdm/gdm-x-session[] 316759
kernel 99202
gnome-software[] 74095
systemd[] 56480
sushi-start[] 33661
NetworkManager[] 29022
org.gnome.Nautilus[] 17196
-- Logs begin at Tue 2018-07-24 03:22:16 +03, end at Wed 2018-10-10
18:23:25 +03. --
If I disable all extensions, log entries becomes silent.. Any idea which
extension is causing this problem? Is there a systematic way to test an
extension for this bug (instead of 1.activate extension 2.check log for
a while 3. turn off the extension 4. go to 1)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1747566
Title:
syslog fills with messages: Object ..., has been already finalized.
Impossible to get any property from it. ... (stack trace in
tweener.js)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1747566/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797052] Re: nautilus no longer notifies when a new drive has been added
Further discussion: https://ubuntuforums.org/showthread.php?t=2403323 An update to gnome-shell (3.30.1-2ubuntu1) fixed the issue. ** Changed in: nautilus (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1797052 Title: nautilus no longer notifies when a new drive has been added To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1797052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730410] Re: Window full-screen size when Firefox starts
This looks more like a feature of the window manager, rather than application-specific bugs. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1730410 Title: Window full-screen size when Firefox starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/1730410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730410] Re: Window full-screen size when Firefox starts
(I added a mutter source package task to reflect this) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1730410 Title: Window full-screen size when Firefox starts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/1730410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797163] [NEW] crashed with no warning no error message
Public bug reported: normal activity searching for a file screen locked nautilus crashed Nautilus has been hurky jerky glitchy for weeks now :( ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 18:38:20 2018 InstallationDate: Installed on 2015-08-23 (1144 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-08-21 (50 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1797163 Title: crashed with no warning no error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1797163/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797158] [NEW] Nautilus fails to show file transfer status when copying from NAS
Public bug reported: When copying a file from a NAS using the AFP protocol the "pie chart" graphic in Nautilus fails to display status of the transfer. Eventually the file is copied to the Ubuntu system correctly. This does not occur when copying from Ubuntu system to the NAS, in that case the progress graph displays the file transfer progress. Description:Ubuntu 18.04.1 LTS nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.4-0~ubuntu18.04.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 11:17:49 2018 InstallationDate: Installed on 2018-05-08 (154 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1797158 Title: Nautilus fails to show file transfer status when copying from NAS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1797158/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796649] Re: gjs-console crashed with SIGABRT in g_assertion_message()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1796649 Title: gjs-console crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1796649/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796451] Re: gjs-console crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1796451 Title: gjs-console crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1796451/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797052] Re: nautilus no longer notifies when a new drive has been added
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1797052 Title: nautilus no longer notifies when a new drive has been added To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1797052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797141] [NEW] gnome-shell frequent restart or crash after unlocking screen or resume from sleep
Public bug reported: First, let me provide necessary information about system or packages System: Ubuntu 18.04.1 LTS Package version: gnome-shell 3.28.3-0ubuntu0.18.04.2 The problem started 3-4 weeks ago (probably after updating several packages via `apt update; apt upgrade` After *almost all* screen unlock or resume from sleep events, this is what happens: * I briefly see the desktop screen (which is security or privacy problem I guess) * then login screen comes up, asking for the password * after I put the password there is a wait (5-10 seconds) * after that there are two possibilities: 1. there's brief flash in screen and then screen goes black. i can not fire up tty consoles and i have to use SysRq Magic keys to reboot the system 2. if it does not crash, I login the system, I see the programs/windows but they're unresponsive for 10-30 seconds. after unresponsive time, gnome-shell restarts and only then system starts to function normally. Then apport-bug is started for gnome-shell, I try to send the crash reports. I'm not sure this is gnome-shell or gdm3 or Xorg problem. But, apport- crash always starts collecting data about gnome-shell, thus I filed report against gnome-shell. I also filed bug report against xorg (https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1797124). Let me provide additional info that might help; - I have nvidia drivers installed in system - gnome-shell produces tons of journal entries (this apport-crash reports are huge, nearly 150 MB and I cannot upload them) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 10 17:10:40 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-06-01 (131 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 annoyance apport-bug bionic gnome-shell rant -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797141 Title: gnome-shell frequent restart or crash after unlocking screen or resume from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797141/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796837] Re: Update to 3.30.1
This bug was fixed in the package gnome-shell - 3.30.1-2ubuntu1 --- gnome-shell (3.30.1-2ubuntu1) cosmic; urgency=medium * Merge with debian (LP: #1796837), remaining changes: + Replace gnome-backgrounds dep with ubuntu-wallpapers and Suggests gnome-themes-standard-data, gnome-backgrounds + Add some Recommends: - ubuntu-session (| gnome-session) to have the ubuntu session available - xserver-xorg-legacy - yaru-theme-gnome-shell for the default ubuntu theming + Update debian/gbp.conf with Ubuntu settings + gnome-shell-common.install: Install Ubuntu mode + gnome-shell-common.prerm: Remove deprecated ubuntu theme alternative + ubuntu/desktop_detect.patch: - add caching for desktop detection to avoid querying the current desktop env variable as iterate through the list each time. For the time of the Shell process, we can expect this env variable to stay stable. + ubuntu/smarter_alt_tab.patch: - quick alt-tab (without showing up the switcher) switch only between the last window of the last 2 applications to be focused instead of raising all windows of those apps. + ubuntu/lightdm-user-switching.patch: - Allow user switching when using LightDM. + ubuntu/lock_on_suspend.patch - Respect Ubuntu's lock-on-suspend setting. + ubuntu/gdm.patch - as gdm is system-wide and not session-wide, ensure gdm has an ubuntu styling by default, not impacting the gnome user session though. + ubuntu/background_login.patch - Change default background color as we modified the default GDM color for our ubuntu session. Change it as well here, still applying the background noise loading. + ubuntu/gdm_alternatives.patch - Add support for GDM3 theme alternatives + ubuntu/block_mode_extension_update.patch - Don't allow ubuntu mode extension to update + optional-hot-corner.patch - enable patch proposed by upstream developer already in package (but not in series) to add a settings for optional hot corner activation. + volume-Add-back-sound-feedback-on-scroll.patch - Fix regression causing missing feedback on volume slider scroll + st-texture-cache-Cancel-sliced-image-loading-on-target-ac.patch - Fix possible crash on cache loading + main-show-an-error-message-on-gnome-shell-crash.patch, global-make-possible-to-set-debug-flags-dynamically.patch, main-increase-the-granularity-of-backtraces-in-SHELL_DEBU.patch, main-add-backtrace-crashes-all-and-backtrace-all.patch, sessionMode-add-support-for-debugFlags-parameter.patch: - Improve debug JS tracing for crash reports + st-scroll-view-Handle-the-case-where-scrollbars-are-NULL.patch, st-scroll-view-Remove-scrollbars-references-on-dispose.patch: - Fix crash on theme changes + ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: - stop searches when requested from UI + debian/rules: - Run dh_translations and work around an issue with Rosetta and plural translations * js-main-Throw-error-if-no-valid-default-stylesheet-is-fou.patch, viewSelector-Cancel-search-on-overview-hidden.patch search-Cancel-search-provider-operations-on-clear.patch search-Ignore-search-provider-results-metas-if-search-is-.patch: Dropped, applied upstream. * ubuntu/search-call-XUbuntuCancel-method-on-providers-when-no-dat.patch: Refreshed. gnome-shell (3.30.1-2) unstable; urgency=medium * Team upload [ Jeremy Bicha ] * Don't ignore test failures * Drop unneeded --buildsystem=meson * Drop unneeded override_dh_install gnome-shell (3.30.1-1) unstable; urgency=medium * Team upload * New upstream release - Drop patches that were applied upstream -- Iain Lane Wed, 10 Oct 2018 09:52:13 +0100 ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1796837 Title: Update to 3.30.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796837/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1521754] Re: documentation of gi.repository.Gtk.Application.run missing
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: pygtk (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1521754 Title: documentation of gi.repository.Gtk.Application.run missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1521754/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796722] Re: Unusual Region & Language settings on Live Session after clicking "Try Ubuntu"
Thanks for your report. Jun Kobayashi wrote: > Steps to Reproduce 3: > 1. boot virtual pc with cosmic-desktop-amd64.iso > 2. wait for Ubiquity dialoge and select "日本語" > 3. click "Ubuntuを試す" button > 4. wait for Live Session > 5. input source selection menu is shown on right of topbar, including >"ja1", "ja2", "ja3" and "ja4" > 6. open Settings app and select "Region & Language" > 7. 4 input sources listed: Japanese, Japanese (PC-98), Japanese (OADG >109A), Japanese (Dvorak) > This setting don't supports inputting Japanese. The fact that Mozc isn't available is indeed an issue. It sounds to me as the same issue as the one reported at bug #1786344. Do you agree on that? Besides that, it's unclear to me how your other observations are problems. If you think they are, please let us know what you think should be the expected behavior in the various examples. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1796722 Title: Unusual Region & Language settings on Live Session after clicking "Try Ubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1796722/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795410] Re: cannot bring up window menu via keybinding (alt-space or otherwise)
Well, after an upgrade and reboot (including mutter 3.30.1-1), 'alt space' now works to bring up the m enu. However, there is no 'Always on visible workspace' option. So I will close this bug as 'fix released' and I have opened bug 1797120. ** Changed in: mutter (Ubuntu) Status: New => Fix Released ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1795410 Title: cannot bring up window menu via keybinding (alt-space or otherwise) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795410/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797120] [NEW] window menu does not include 'always on visible workspace'
Public bug reported: I filed bug 1795410 a few weeks ago complaining that the 'alt space' didn't bring up the window menu. That is now fixed (seemingly likely with mutter 3.3.0-6). However, the window menu that does come up does not have an entry for 'Always on visible workspace' as it used to. You can still create a custom shortcut in the gnome-control-center to toggle this, but that is not as useful or discoverable as in the window menu. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 09:21:40 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (1175 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1797120 Title: window menu does not include 'always on visible workspace' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1797120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796722] Re: Unusual Region & Language settings on Live Session after clicking "Try Ubuntu"
** Package changed: ubiquity (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1796722 Title: Unusual Region & Language settings on Live Session after clicking "Try Ubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1796722/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1796722] [NEW] Unusual Region & Language settings on Live Session after clicking "Try Ubuntu"
You have been subscribed to a public bug: I've faced this problem when I tried Cosmic daily iso with VirtualBox. iso image: http://cdimage.ubuntu.com/daily-live/20181007/cosmic-desktop- amd64.iso Steps to Reproduce 1: 1. boot virtual pc with cosmic-desktop-amd64.iso 2. wait for Ubiquity dialoge 3. click "Try Ubuntu" button 4. wait for Live Session 5. input source selection menu is shown on right of topbar, including "en1", "en2", "cm" and "en3" 6. open Settings app and select "Region & Language" 7. 4 input sources listed: English(US), English(Australian), English(Cameroon), English(UK) Steps to Reproduce 2: 1. boot virtual pc with cosmic-desktop-amd64.iso 2. wait for Ubiquity dialoge and select "Deutsch" 3. click "Ubuntu ausprobieren" button 4. wait for Live Session 5. input source selection menu is shown on right of topbar, including "de1", "de2", "be" and "de3" 6. open Einstellungen app and select "Region und Sprache" 7. 4 input sources listed: Deutsch, Deutsch (Österreich), Belgisch, Deutsch (Schweiz) "English (United States)" for Sprache, "United States" for Formate Steps to Reproduce 3: 1. boot virtual pc with cosmic-desktop-amd64.iso 2. wait for Ubiquity dialoge and select "日本語" 3. click "Ubuntuを試す" button 4. wait for Live Session 5. input source selection menu is shown on right of topbar, including "ja1", "ja2", "ja3" and "ja4" 6. open Settings app and select "Region & Language" 7. 4 input sources listed: Japanese, Japanese (PC-98), Japanese (OADG 109A), Japanese (Dvorak) This setting don't supports inputting Japanese. When I selected "Try Ubuntu without installing" on isolinux menu and login directly into Live Session, only "English (US)" is shown for input source.This seem to be normal setting. When I selected "Deutsch" and boot Live Session, only "Deutsch" is shown for input source. When I selected "日本語" and boot Live Session, "Japanese" and "日本語(Mozc)" are shown.This setting supports inputting Japanese. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubiquity 18.10.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CasperVersion: 1.396 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 17:11:12 2018 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181007) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic iso-testing ubiquity-18.10.9 ubuntu -- Unusual Region & Language settings on Live Session after clicking "Try Ubuntu" https://bugs.launchpad.net/bugs/1796722 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795637] Re: No login screen when booting Cosmic
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1795637 Title: No login screen when booting Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1795637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795637] Re: No login screen when booting Cosmic
I think it's like this (line numbers added) bad: line 423: [ply-boot-server.c:388] print_connection_process_identity:connection is from pid 677 (/bin/plymouth deactivate) with parent pid 668 (/usr/sbin/gdm3) line 498: [./plugin.c:649] activate:taking master and scanning out good: line 402: [./plugin.c:649] activate:taking master and scanning out line 573: [ply-boot-server.c:388] print_connection_process_identity:connection is from pid 711 (/bin/plymouth deactivate) with parent pid 665 (/usr/sbin/gdm3) line 583: [./plugin.c:679] deactivate:dropping master In the bad case, we don't see "dropping master" because boot_splash is NULL, because we were already deactivated. I asked upstream about the attached patch, will see what they say and in the meantime it's on https://launchpad.net/~laney/+archive/ubuntu/plymouth if somebody would care to test. ** Patch added: "0001-Don-t-show-default-splash-if-we-are-already-inactive.patch" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1795637/+attachment/5199439/+files/0001-Don-t-show-default-splash-if-we-are-already-inactive.patch ** Changed in: plymouth (Ubuntu Cosmic) Status: New => Triaged ** Changed in: plymouth (Ubuntu Cosmic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1795637 Title: No login screen when booting Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1795637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1768166] Re: Random crashes
** Also affects: libpinyin (Ubuntu) Importance: Undecided Status: New ** Also affects: language-selector (Ubuntu) Importance: Undecided Status: New ** Also affects: language-selector (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libpinyin (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ibus-libpinyin (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: language-selector (Ubuntu Bionic) ** No longer affects: language-selector (Ubuntu) ** Changed in: ibus-libpinyin (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: ibus-libpinyin (Ubuntu Bionic) Status: New => In Progress ** Changed in: ibus-libpinyin (Ubuntu Bionic) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: libpinyin (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: libpinyin (Ubuntu Bionic) Status: New => In Progress ** Changed in: libpinyin (Ubuntu Bionic) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) ** Changed in: ibus-libpinyin (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libpinyin (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1768166 Title: Random crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797052] Re: nautilus no longer notifies when a new drive has been added
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1797052 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1797052 Title: nautilus no longer notifies when a new drive has been added To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1797052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797059] [NEW] Update to 1.9.0 next cycle
Public bug reported: The new version has changes that are not trivial, let's delay to next cycle ** Affects: harfbuzz (Ubuntu) Importance: Wishlist Status: Triaged ** Tags: upgrade-software-version version-blocked-ff ** Changed in: harfbuzz (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to harfbuzz in Ubuntu. https://bugs.launchpad.net/bugs/1797059 Title: Update to 1.9.0 next cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/harfbuzz/+bug/1797059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1728184] Re: Please remove mozjs38 from Ubuntu
Removing packages from cosmic: mozjs38 38.8.0~repack1-0ubuntu4 in cosmic libmozjs-38-0 38.8.0~repack1-0ubuntu4 in cosmic amd64 libmozjs-38-0 38.8.0~repack1-0ubuntu4 in cosmic arm64 libmozjs-38-0 38.8.0~repack1-0ubuntu4 in cosmic armhf libmozjs-38-0 38.8.0~repack1-0ubuntu4 in cosmic i386 libmozjs-38-0 38.8.0~repack1-0ubuntu4 in cosmic ppc64el libmozjs-38-0 38.8.0~repack1-0ubuntu4 in cosmic s390x libmozjs-38-dev 38.8.0~repack1-0ubuntu4 in cosmic amd64 libmozjs-38-dev 38.8.0~repack1-0ubuntu4 in cosmic arm64 libmozjs-38-dev 38.8.0~repack1-0ubuntu4 in cosmic armhf libmozjs-38-dev 38.8.0~repack1-0ubuntu4 in cosmic i386 libmozjs-38-dev 38.8.0~repack1-0ubuntu4 in cosmic ppc64el libmozjs-38-dev 38.8.0~repack1-0ubuntu4 in cosmic s390x Comment: deprecated by newer versions, no rdepends (lp: #1728184) Remove [y|N]? y 1 package successfully removed. ** Changed in: mozjs38 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mozjs38 in Ubuntu. https://bugs.launchpad.net/bugs/1728184 Title: Please remove mozjs38 from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs38/+bug/1728184/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797052] [NEW] nautilus no longer notifies when a new drive has been added
Public bug reported: Very recently I have noticed that nautilus no longer notifies me when I add a new USB drive to my PC. I do receive other notifications however. To reproduce: Insert USB stick into appropriate slot or switch on external drive. What should happen: An on screen notification should appear underneath GNOME Shell's date applet. What does happen: Drive is added but no notification appears. This seems to be a recent change as tests done with the beta ISO show that notifications were received. Testing ISO 20181009 in a live session on two PCs implies a recent change since the beta. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu6 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 10 08:30:34 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'166' b'org.gnome.nautilus.window-state' b'geometry' b"'625x479+447+122'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2018-10-02 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181002) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1797052 Title: nautilus no longer notifies when a new drive has been added To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1797052/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1745666] Re: gsd-housekeeping leaks file descriptors
I just tried to report this bug for Bionic, it informed me the package was not installed when i used fn+alt f2 ubuntu-bug gsd-housekeepin. I have changed the computer name in the output but had a privlige issue Oct 10 01:47:36 Ze-C00mp7er-Name-Duh kernel: [79249.397167] [UFW BLOCK]... Oct 10 01:48:00 Ze-C00mp7er-Name-Duh gsd-housekeepin[1697]: Failed to enumerate children of /var/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-fwupd.service-mpR5zs: Error opening directory '/var/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-fwupd.service-mpR5zs': Permission denied Oct 10 01:48:00 Ze-C00mp7er-Name-Duh gsd-housekeepin[1697]: Failed to enumerate children of /var/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-rtkit-daemon.service-OpMdvp: Error opening directory '/var/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-rtkit-daemon.service-OpMdvp': Permission denied Oct 10 01:48:00 Ze-C00mp7er-Name-Duh gsd-housekeepin[1697]: Failed to enumerate children of /var/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-colord.service-iqprAr: Error opening directory '/var/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-colord.service-iqprAr': Permission denied Oct 10 01:48:00 Ze-C00mp7er-Name-Duh gsd-housekeepin[1697]: Failed to enumerate children of /var/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-bolt.service-ieEFMJ: Error opening directory '/var/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-bolt.service-ieEFMJ': Permission denied Oct 10 01:48:00 Ze-C00mp7er-Name-Duh gsd-housekeepin[1697]: Failed to enumerate children of /var/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-systemd-resolved.service-ckArYi: Error opening directory '/var/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-systemd-resolved.service-ckArYi': Permission denied Oct 10 01:48:00 Ze-C00mp7er-Name-Duh gsd-housekeepin[1697]: Failed to enumerate children of /var/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-systemd-timesyncd.service-CdKRqO: Error opening directory '/var/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-systemd-timesyncd.service-CdKRqO': Permission denied Oct 10 01:48:00 Ze-C00mp7er-Name-Duh gsd-housekeepin[1697]: Failed to enumerate children of /tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-fwupd.service-Bmog5W: Error opening directory '/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-fwupd.service-Bmog5W': Permission denied Oct 10 01:48:00 Ze-C00mp7er-Name-Duh gsd-housekeepin[1697]: Failed to enumerate children of /tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-colord.service-FegyGA: Error opening directory '/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-colord.service-FegyGA': Permission denied Oct 10 01:48:00 Ze-C00mp7er-Name-Duh gsd-housekeepin[1697]: Failed to enumerate children of /tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-bolt.service-1zMUMT: Error opening directory '/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-bolt.service-1zMUMT': Permission denied Oct 10 01:48:00 Ze-C00mp7er-Name-Duh gsd-housekeepin[1697]: Failed to enumerate children of /tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-rtkit-daemon.service-PGWz5B: Error opening directory '/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-rtkit-daemon.service-PGWz5B': Permission denied Oct 10 01:48:00 Ze-C00mp7er-Name-Duh gsd-housekeepin[1697]: Failed to enumerate children of /tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-systemd-resolved.service-F7qEHy: Error opening directory '/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-systemd-resolved.service-F7qEHy': Permission denied Oct 10 01:48:00 Ze-C00mp7er-Name-Duh gsd-housekeepin[1697]: Failed to enumerate children of /tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-systemd-timesyncd.service-rlCla4: Error opening directory '/tmp/systemd-private-6465a9cfaab745e3be21bfacf5191d7d-systemd-timesyncd.service-rlCla4': Permission denied Oct 10 01:48:07 Ze-C00mp7er-Name-Duh kernel: [79279.812157] [UFW BLOCK] ... Note the UFW blocks are Apple devices doing multicast traffic. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1745666 Title: gsd-housekeeping leaks file descriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1745666/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
