[Desktop-packages] [Bug 1551515] Re: My phone's bluetooth is displayed dozens of times under the network list (wifi icon)
Still an issue in 20.04. Fucking unbelievable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1551515 Title: My phone's bluetooth is displayed dozens of times under the network list (wifi icon) Status in One Hundred Papercuts: Confirmed Status in NetworkManager: New Status in network-manager package in Ubuntu: Confirmed Bug description: I can hardly even start describing how screwed up this is. Have a look at the screenshot. I had seen this before and hadn't even realized that "XT1039 Network" repeated like 37 times had something to do with my own Android phone, a motorola Moto G. Needless to say I have only one. Out of curiosity I clicked on one of "them" (thinking this was some neighboor's device, obviously suspecting it was just one device repeated several times because of a bug), and then my phone vibrated prompting me whether to accept the connection from the computer. Which I did. As a result, the bluetooth indicator next to the network indicator showed a lock icon for a fraction of a second, which immediately disappeared. I guess that means that the computer and the phone peered via bluetooth for a few instants. At the same time, the wifi icon started animating (as if the computer was connecting to a wifi network... or a network of any kind I guess, since the same stupidly designed wifi-like animation is used when connecting to LAN via an ethernet cable). After that, the small lock below the bluetooth icon disappeared, the wifi icon stopped animating and went back to its normal "connected" status (I was previously and still connected to my home router's wifi network), and a baloon saying "Disconnected [NL] Network" appeared and disappeared. Then I repeated the test several times with the same result, except that the phone didn't prompt me any more to accept the connection. This is totally screwed up in several ways. First, there's no reason "XT1039 Network" should be listed AT ALL together with wifi and ethernet networks. What kind of "network" is it supposed to be?? Of course I have not turned on bluetooth tethering on the phone, and bluetooth connection to the phone is already available under the bluetooth indicator. If it makes any sense at all to show the mobile device as a "network" alongside with wifi and cable networks because, well, bluetooth is a network as well, then 1) the list of bluetooth "networks" should have a header, just like "wifi networks" and "ethernet network". Right now, there is just a list of networks that you don't know what kind they are 2) the device should be only listed once, not 37 times 3) I also suspect the 3 items called just "network" are related 4) If it is there at all, it must work. What is it supposed to do? The same as unfolding the menu under the Bluetooth indicator, hovering on the device there (which is listed only once there) and turning on the "Connection" switch? That one does work. This one (in the list of networks) doesn't. And if it is supposed to do something different, it's clearly failing as well. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.2 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 1 03:29:50 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (871 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.167 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2016-01-18 (42 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-20T16:52:59.722501 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1551515/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 911981] Re: tracker-store uses 100% cpu and fills all the disk space in home partition
I'm having this issue. I googled for the name of the process that was eating up 100% of CPU and, surprise! A bug reported in 20-fucking-12 and still not fixed! Great job, Ubuntu! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/911981 Title: tracker-store uses 100% cpu and fills all the disk space in home partition Status in tracker package in Ubuntu: Confirmed Bug description: I recently noticed that several tracker related programs were using 100% cpu on my system and in particular tracker-store filled up completely all the available disk space in my home partition. I rerun tracker-preferences to make sure that indexing would not proceed if less than 20% of free space is available, but it seems that tracker-store ignores it. After I noticed that I had left only 44Kb free on the home partition, I deleted the cache from another program and I noticed that tracker-store filled up again the disk space that I freed few minutes before. This is the content of my .cache/tracker/ directory: totale 772068 -rw-r--r-- 1 eclipse eclipse 3072 2011-06-26 22:56 contents.db -rw-r--r-- 1 eclipse eclipse11 2012-01-04 21:24 db-locale.txt -rw-r--r-- 1 eclipse eclipse 2 2011-12-12 04:02 db-version.txt -rw-r--r-- 1 eclipse eclipse 3072 2010-12-05 21:29 email-contents.db -rw-r--r-- 1 eclipse eclipse 3072 2009-05-06 19:16 email-fulltext.db -rw-r--r-- 1 eclipse eclipse 2359292 2011-06-26 22:54 email-index.db -rw-r--r-- 1 eclipse eclipse 34816 2010-12-05 21:29 email-meta.db -rw-r--r-- 1 eclipse eclipse 17062912 2011-06-26 19:30 file-contents.db -rw-r--r-- 1 eclipse eclipse 15014912 2010-01-12 20:26 file-fulltext.db -rw-r--r-- 1 eclipse eclipse 75609207 2011-06-26 22:54 file-index.db -rw-r--r-- 1 eclipse eclipse 37027840 2011-06-26 19:31 file-meta.db -rw--- 1 eclipse eclipse 1180048 2009-05-05 22:57 file-update-index.db -rw-r--r-- 1 eclipse eclipse 28376064 2011-10-20 09:34 fulltext.db -rw-r--r-- 1 eclipse eclipse 1024 2012-01-04 21:24 meta.db -rw-r--r-- 1 eclipse eclipse 4653056 2012-01-04 21:26 meta.db-shm -rw-r--r-- 1 eclipse eclipse 608064304 2012-01-04 21:26 meta.db-wal -rw-r--r-- 1 eclipse eclipse11 2011-12-12 04:02 miner-applications-locale.txt -rw-r--r-- 1 eclipse eclipse345110 2012-01-04 21:24 ontologies.gvdb and this is how much space I have left on my home partition after I KILLED the tracker-store process: /dev/sda8 31G 30G 418M 99% /home --- ApportVersion: 1.23-0ubuntu4 Architecture: i386 DistroRelease: Ubuntu 11.10 Package: tracker 0.10.24-1build2 PackageArchitecture: i386 ProcEnviron: LANGUAGE=it_IT:it:en_GB:en PATH=(custom, user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric Uname: Linux 3.0.0-14-generic i686 UpgradeStatus: Upgraded to oneiric on 2011-10-20 (76 days ago) UserGroups: adm admin audio cdrom dip fuse lpadmin plugdev polkituser pulse-access sambashare src video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/911981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887296] Re: Moving popup windows drags the application's main window behind it
> We do not consider Gnome's defaults in this area unreasonable. That no longer surprises me. Ubuntu apparently has stopped fighting the idiotic decisions taken by Gnome upstream. You are no longer patching the type-ahead-triggers-search madness, you refused to restore the "open with" submenu, you have embraced the reversed sorting icons, and the list goes on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1887296 Title: Moving popup windows drags the application's main window behind it Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Sometimes programs open a "popup" or a "secondary", "child" window, I don't know what the word is. For example, in Chrome, if I right-click on an image in a web page and choose "Save As", this will open a new file browser window that allows me to browse for a directory to save the image to. Until Ubuntu 16.04, I could move that child window around by dragging it by its title bar, and that would not move around the parent window behind it. Now, it does. That is, the "parent" window greyes out, and moving the "child" window (i.e. the popup) on the foreground causes the parent window in the background to move as if they were glued together. In the above example, if I drag around the "Save As" window, the Chrome window behind it moves too. Even worse, if the parent window is maximized, it will "oppose resistance" to the dragging of the popup window, and if I drag far enough, the parent window will unmaximize and unblock the movement of both windows. It's pure madness. I can't imagine a scenario where this is the unavoidable consequence of some improvement. It looks like it is by design. Why? What were you thinking? Why do you ACTIVELY work to degrade usability and make the users' life miserable?? Here's a very real-life example: As mentioned above, I right-click on something in the browser (like an image or a video) and do Save As. When the file browser window opens, it covers the content of the web page from which I was saving the content. Maybe I want to move the child window in order to reveal the web page that I was visiting in the first place, because the context (which I haven't memorized in full in my brain just yet) helps me choose a file name for the very file I'm saving. Another example: I am browsing some folder in Nautilus. I right-click on a file or folder inside it, and open Properties. That opens in a popup. Now I want to have another look at the name of the file I selected (of which I'm now seeing the properties), and those around it, because I'm wondering if I chose the wrong file, or for whatever other reason. I can't do taht without closing the Properties window. The everyday examples are countless. This is idiotic. Seriously, what are you doing? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 18:11:28 2020 DistUpgraded: 2020-07-12 15:56:23,368 INFO cache.commit() DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108: added ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag
[Desktop-packages] [Bug 1647217] Re: Nautilus “Open with …” context menu gone on upgrade to yakkety
> the current maintainers are quite open to comments LOL you're kidding right? Not only they're not open to comments, they are not even willing to recognize their mistakes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1647217 Title: Nautilus “Open with …” context menu gone on upgrade to yakkety Status in nautilus package in Ubuntu: Won't Fix Bug description: Release: 16.10 Package:nautilus, 1:3.20.3-1ubuntu3.1 Expected behaviour: 1. Open Files 2. Right-click on icon, move to "Open with …", and pick suitable app from an immediate list 3. File opens in selected application. This was standard behaviour on 16.04, and is expected behaviour from Windows and Mac OS. Actual behaviour: 1. Open Files 2. Right-click on icon, note lack of "Open with …" option, and select "Open With Other Application" 3. "Select Application" window opens instead of immediate list. Window contains long list 4. Scroll down list until application appears, select it, and file opens in selected application. This is a usability regression. No explanation is given why this is gone, or how to recover the (expected, standard, rational) previous behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 4 17:01:37 2016 InstallationDate: Installed on 2015-03-08 (637 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-12-02 (2 days ago) usr_lib_nautilus: dropbox2015.10.28 gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1647217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1647217] Re: Nautilus “Open with …” context menu gone on upgrade to yakkety
You seriously need to either fork Gnome or replace it with something else. It's RUINING Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1647217 Title: Nautilus “Open with …” context menu gone on upgrade to yakkety Status in nautilus package in Ubuntu: Won't Fix Bug description: Release: 16.10 Package:nautilus, 1:3.20.3-1ubuntu3.1 Expected behaviour: 1. Open Files 2. Right-click on icon, move to "Open with …", and pick suitable app from an immediate list 3. File opens in selected application. This was standard behaviour on 16.04, and is expected behaviour from Windows and Mac OS. Actual behaviour: 1. Open Files 2. Right-click on icon, note lack of "Open with …" option, and select "Open With Other Application" 3. "Select Application" window opens instead of immediate list. Window contains long list 4. Scroll down list until application appears, select it, and file opens in selected application. This is a usability regression. No explanation is given why this is gone, or how to recover the (expected, standard, rational) previous behaviour. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: nautilus 1:3.20.3-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 4 17:01:37 2016 InstallationDate: Installed on 2015-03-08 (637 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: nautilus UpgradeStatus: Upgraded to yakkety on 2016-12-02 (2 days ago) usr_lib_nautilus: dropbox2015.10.28 gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1647217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887285] Re: Restore the "open with" submenu
This is at least medium: - A bug that has a moderate impact on a core application. - A usability issue that does not limit the functionality of a core application. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887285 Title: Restore the "open with" submenu Status in nautilus package in Ubuntu: New Bug description: Up until a few hours ago I was using Ubuntu 16.04. When right-clicking on a file in Nautilus, the context menu used to have a submenu, right next to the "open with " option, called "open with...", where the items in the submenu were the most common applications. Half of the times I open files with some of those (but the other half I do open the same file with the default application, so changing the default is not good enough for me, also I don't like to do that). So, having the submenu was very useful to me (and millions of other users). After upgrading to 18.10 and now 19.10, that submenu is gone. Now you have to click on "open with another application", wait for a completely separate, bloated popup to load and show up somewhere else, and then select the application to open the file with. This looks like it can only have been done by design, so I guess it's yet another idiotic decision made by the lunatics that maintain Nautilus, who clearly don't give two minutes of thought to what they are doing. This is ridiculous and has to be reverted. Since it has been proven that upstream Gnome developers can't be trusted to have any common sense and hence are very unlikely to be inclined to fix this, if Ubuntu insists in keeping Nautilus as the chosen default file manager, Ubuntu should patch this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:21:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2020-07-12 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887285/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887446] Re: Area of desktop behind the Launcher is filled with random noise
Actually, now that I've been able to restore the shortcut for showing desktop (yeah, I could have minimized all the windows manually one by one), I realize that MY ENTIRE FUCKING DESKTOP is filled with noise. I attach a screenshot of the whole desktop (I blurred out the icons) ** Attachment added: "Screenshot from 2020-07-14 01-37-20.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887446/+attachment/5392430/+files/Screenshot%20from%202020-07-14%2001-37-20.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887446 Title: Area of desktop behind the Launcher is filled with random noise Status in xorg package in Ubuntu: New Bug description: The screenshot speaks for itself. Stuff like this used to happen occasionally up to 16.04, sually after resuming from suspend, but normally the areas would get redrawn properly sooner or later. But since I upgraded to 20.04 I've seen display garbage like this a lot more often, and this particular instance has been like this for hours now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 13 18:51:51 2020 DistUpgraded: 2020-07-12 20:55:12,554 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2466 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Jul 12 20:59:51 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1887446] [NEW] Area of desktop behind the Launcher is filled with random noise
Public bug reported: The screenshot speaks for itself. Stuff like this used to happen occasionally up to 16.04, sually after resuming from suspend, but normally the areas would get redrawn properly sooner or later. But since I upgraded to 20.04 I've seen display garbage like this a lot more often, and this particular instance has been like this for hours now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 13 18:51:51 2020 DistUpgraded: 2020-07-12 20:55:12,554 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2466 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Jul 12 20:59:51 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu ** Attachment added: "Screenshot from 2020-07-13 18-51-36.png" https://bugs.launchpad.net/bugs/1887446/+attachment/5392401/+files/Screenshot%20from%202020-07-13%2018-51-36.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887446 Title: Area of desktop behind the Launcher is filled with random noise Status in xorg package in Ubuntu: New Bug description: The screenshot speaks for itself. Stuff like this used to happen occasionally up to 16.04, sually after resuming from suspend, but normally the areas would get redrawn properly sooner or later. But since I upgraded to 20.04 I've seen display garbage like this a lot more often, and this particular instance has been like this for hours now. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0:
[Desktop-packages] [Bug 1887296] Re: Moving popup windows drags the application's main window behind it
> This is a feature we inherited from GNOME. It is not a design choice by Ubuntu. Ubuntu is responsible for what it distributes. I don't care whether the solution involves reporting this upstream and having them fix it, or applying a patch, or a setting other than the upstream default in Ubuntu. Ubuntu's job is to provide a distribution that works. If gnome comes with unreasonable defaults, you should override them, or replace Gnome with something else. > To disable it just set: > > Gnome Tweaks > Windows > Attach Modal Dialogs = OFF I shouldn't have to install an additional package + tweak a system setting just to get the sensible behavior. The sensible behavior should be out of the box. Tweaking settings (and even worse, having to install additional software to do so) should be reserved for preferences that are different from the most common and normal setting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1887296 Title: Moving popup windows drags the application's main window behind it Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Sometimes programs open a "popup" or a "secondary", "child" window, I don't know what the word is. For example, in Chrome, if I right-click on an image in a web page and choose "Save As", this will open a new file browser window that allows me to browse for a directory to save the image to. Until Ubuntu 16.04, I could move that child window around by dragging it by its title bar, and that would not move around the parent window behind it. Now, it does. That is, the "parent" window greyes out, and moving the "child" window (i.e. the popup) on the foreground causes the parent window in the background to move as if they were glued together. In the above example, if I drag around the "Save As" window, the Chrome window behind it moves too. Even worse, if the parent window is maximized, it will "oppose resistance" to the dragging of the popup window, and if I drag far enough, the parent window will unmaximize and unblock the movement of both windows. It's pure madness. I can't imagine a scenario where this is the unavoidable consequence of some improvement. It looks like it is by design. Why? What were you thinking? Why do you ACTIVELY work to degrade usability and make the users' life miserable?? Here's a very real-life example: As mentioned above, I right-click on something in the browser (like an image or a video) and do Save As. When the file browser window opens, it covers the content of the web page from which I was saving the content. Maybe I want to move the child window in order to reveal the web page that I was visiting in the first place, because the context (which I haven't memorized in full in my brain just yet) helps me choose a file name for the very file I'm saving. Another example: I am browsing some folder in Nautilus. I right-click on a file or folder inside it, and open Properties. That opens in a popup. Now I want to have another look at the name of the file I selected (of which I'm now seeing the properties), and those around it, because I'm wondering if I chose the wrong file, or for whatever other reason. I can't do taht without closing the Properties window. The everyday examples are countless. This is idiotic. Seriously, what are you doing? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 18:11:28 2020 DistUpgraded: 2020-07-12 15:56:23,368 INFO cache.commit() DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108: added ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
[Desktop-packages] [Bug 1887304] [NEW] Display configuration gets applied only after I log in
Public bug reported: This isn't new, this idiocy has annoyed me ever since I've been using Ubuntu; however, after upgrading to 20.04 I'm disappointed to see that it still hasn't been fixed. I use a laptop and I have an external monitor that I keep connected most of the time. So, I have it set up to use the external screen as the only display. However, when I boot and the login screen shows up, a different configuration, which I guess is the default, is applied, with the laptop's built-in display as the main display and the external screen as the secondary one in extended desktop configuration. Therefore the login screen shows up on the builtin display. Only after I log in, my configuration gets applied and the builtin displey turns off and the external one becomes the only one. It's not a huge deal since the laptop screen is kind of in front of me anyway so I can see it, but it's not ideal and it's stupid. Also, it implies that when I do log in, I have that few seconds of all-black screens while the displays adjust, which is irritating considered they would have had plenty of time to do that before I logged in. I guess the display configuration is somehow stored as associated to the user, and I understand that theoretically different users may have different configurations. However, that's no excuse. As an administrator, I should be able to choose a configuration that gets applied from the beginning before anybody logs in. Also, given that I am the ONLY user (which is a pretty common scenario on Desktop), it should be the default that my configuration be the global configuration (with the possibility to choose differently). Probably a good solution would be to have, in the Displays settings, an option such as "apply this configuration globally" (or whatever better phrasing), meaning it would be applied before login. Obviously that doesn't mean that, if the saved configuration is not applicable to the current situation at startup (e.g. I have set it up to use only the external monitor but there is no external monitor connected right now), it shouldn't automatically switch to a different workable setting. I think it already does that if that happens after login, so that would be no different before login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 21:04:20 2020 DistUpgraded: 2020-07-12 20:55:12,554 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2466 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri:
[Desktop-packages] [Bug 1887296] [NEW] Moving popup windows drags the application's main window behind it
Public bug reported: Sometimes programs open a "popup" or a "secondary", "child" window, I don't know what the word is. For example, in Chrome, if I right-click on an image in a web page and choose "Save As", this will open a new file browser window that allows me to browse for a directory to save the image to. Until Ubuntu 16.04, I could move that child window around by dragging it by its title bar, and that would not move around the parent window behind it. Now, it does. That is, the "parent" window greyes out, and moving the "child" window (i.e. the popup) on the foreground causes the parent window in the background to move as if they were glued together. In the above example, if I drag around the "Save As" window, the Chrome window behind it moves too. Even worse, if the parent window is maximized, it will "oppose resistance" to the dragging of the popup window, and if I drag far enough, the parent window will unmaximize and unblock the movement of both windows. It's pure madness. I can't imagine a scenario where this is the unavoidable consequence of some improvement. It looks like it is by design. Why? What were you thinking? Why do you ACTIVELY work to degrade usability and make the users' life miserable?? Here's a very real-life example: As mentioned above, I right-click on something in the browser (like an image or a video) and do Save As. When the file browser window opens, it covers the content of the web page from which I was saving the content. Maybe I want to move the child window in order to reveal the web page that I was visiting in the first place, because the context (which I haven't memorized in full in my brain just yet) helps me choose a file name for the very file I'm saving. Another example: I am browsing some folder in Nautilus. I right-click on a file or folder inside it, and open Properties. That opens in a popup. Now I want to have another look at the name of the file I selected (of which I'm now seeing the properties), and those around it, because I'm wondering if I chose the wrong file, or for whatever other reason. I can't do taht without closing the Properties window. The everyday examples are countless. This is idiotic. Seriously, what are you doing? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 18:11:28 2020 DistUpgraded: 2020-07-12 15:56:23,368 INFO cache.commit() DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108: added ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
[Desktop-packages] [Bug 1887287] [NEW] No show-desktop shortcut out of the box since 18.04
Public bug reported: On Ubuntu 16.04 I was used to the keyboard shortcut ctrl+Super+D to reveal the Desktop by minimizing all windows (it was not exactly the same as minimizing all windows but whatever). That shortcut was changed at almost every major release, which was already irritating enough, but at least there always was one. Now, however, there doesn't seem to be any half-discoverable keyboard shortcut to show the desktop. I have tried Super+D, Ctrl+Alt+D (both mentioned in a bullshit article I found out by googling), and every other similar combination I can think of involving a D. Nothing works. I shouldn't have to install a tool and create a shortcut to it just to reveal the desktop. It's something basic. Especially considering that it used to be available out of the box. So sick of Ubuntu going backwards. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:30:58 2020 DistUpgraded: 2020-07-12 15:02:52,488 DEBUG running apport_crash() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 4.15.0-109-generic, x86_64: installed nvidia-340, 340.108, 4.4.0-185-generic, x86_64: installed nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2020-07-12 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Jul 12 15:12:31 2020 xserver.configfile: default xserver.errors: modeset(G0): eglGetDisplay() failed modeset(G0): glamor initialization failed NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.5+git20191008-0ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887287 Title: No show-desktop shortcut out of the box since 18.04 Status in xorg package in Ubuntu: New Bug description: On Ubuntu 16.04 I was used to the keyboard shortcut ctrl+Super+D to reveal the Desktop by minimizing all windows (it was not exactly the same as minimizing all windows but whatever). That shortcut was changed at
[Desktop-packages] [Bug 1887285] [NEW] Restore the "open with" submenu
Public bug reported: Up until a few hours ago I was using Ubuntu 16.04. When right-clicking on a file in Nautilus, the context menu used to have a submenu, right next to the "open with " option, called "open with...", where the items in the submenu were the most common applications. Half of the times I open files with some of those (but the other half I do open the same file with the default application, so changing the default is not good enough for me, also I don't like to do that). So, having the submenu was very useful to me (and millions of other users). After upgrading to 18.10 and now 19.10, that submenu is gone. Now you have to click on "open with another application", wait for a completely separate, bloated popup to load and show up somewhere else, and then select the application to open the file with. This looks like it can only have been done by design, so I guess it's yet another idiotic decision made by the lunatics that maintain Nautilus, who clearly don't give two minutes of thought to what they are doing. This is ridiculous and has to be reverted. Since it has been proven that upstream Gnome developers can't be trusted to have any common sense and hence are very unlikely to be inclined to fix this, if Ubuntu insists in keeping Nautilus as the chosen default file manager, Ubuntu should patch this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:21:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to eoan on 2020-07-12 (0 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1887285 Title: Restore the "open with" submenu Status in nautilus package in Ubuntu: New Bug description: Up until a few hours ago I was using Ubuntu 16.04. When right-clicking on a file in Nautilus, the context menu used to have a submenu, right next to the "open with " option, called "open with...", where the items in the submenu were the most common applications. Half of the times I open files with some of those (but the other half I do open the same file with the default application, so changing the default is not good enough for me, also I don't like to do that). So, having the submenu was very useful to me (and millions of other users). After upgrading to 18.10 and now 19.10, that submenu is gone. Now you have to click on "open with another application", wait for a completely separate, bloated popup to load and show up somewhere else, and then select the application to open the file with. This looks like it can only have been done by design, so I guess it's yet another idiotic decision made by the lunatics that maintain Nautilus, who clearly don't give two minutes of thought to what they are doing. This is ridiculous and has to be reverted. Since it has been proven that upstream Gnome developers can't be trusted to have any common sense and hence are very unlikely to be inclined to fix this, if Ubuntu insists in keeping Nautilus as the chosen default file manager, Ubuntu should patch this. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:21:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
[Desktop-packages] [Bug 1887247] Re: Annoying drum sound that I turned off ages ago has turned on again after upgrade
> Note: Please watch your language. They're serious about that here I know, I wish they were half as serious about handling bugs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887247 Title: Annoying drum sound that I turned off ages ago has turned on again after upgrade Status in xorg package in Ubuntu: New Bug description: I have just upgraded from 16.04 to 18.04 Now, every time I hit the TAB key in a terminal to autocomplete a file name, when there is no option or more than one, an annoying and ungodly loud drum sound plays. I'm pretty sure I disabled that sound years ago, probably even before I even upgraded to 16.04. I don't want to be forced to re-configure everything. If I turned off a certain kind of system sounds, I expect this configuration to be kept after I upgrade to a newer release. Otherwise I might as well wipe out my hard disk and do a clean install, if you are going to reset my settings anyway. And by the way, if the sound had been chosen with a minimum of taste and was not disproportionately loud (my global volume is pretty low) I probably wouldn't need to turn it off in the first place, as in principle it can be useful. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 20:48:14 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 4.15.0-109-generic, x86_64: installed nvidia-340, 340.108, 4.4.0-185-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Jul 11 20:18:24 2020 xserver.configfile: default xserver.errors: modeset(G0): eglGetDisplay() failed modeset(G0): glamor initialization failed NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887247/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1887254] Re: The new design makes maximized windows unusable
And by the way, this idiocy of having the system bar PLUS the maximized window's top bar (which used to be one) eats up a significant amount of vertical space, and gives ZERO extra functionality. There's a lot of empty space in both, and they contain the exact same elements that were already there, only rearranged differently, with the only exception of the "Activities" thing which I guess I'll learn is very useful, but could have been a small icon that could have fit in the original design without adding a whole extra line. Unbelievable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887254 Title: The new design makes maximized windows unusable Status in xorg package in Ubuntu: New Bug description: I have just upgraded from ubuntu 16.04 to 18.04 (and I would have upgraded to 20.04 already if the stupid package manager weren't unable to resolve some conflicts which are "holding back" packages). An unbelievavly stupid mistake was made in the new design of windows. When you maximize a window, the title bar used to be at the very top of the screen, and the close/minimize/restore buttons used to be at the top-left corner of the screen. That means they had a property that in interface design has even a name, "infinite width" or "infinite something", that is: you can move the mouse all the way to the top and all the way to the left without having to "stop at the right time" in order to "land" within the area of the button, because the screen edges limit the mouse cursor. Now, the title bar of the window is no longer at the very top of the screen. At the top of the screen is a system bar. I mean that was already there, but the window buttons used to be in it on the left, as if the system bar at the top of the screen *was* the window title bar. Now the window title bar is just below it, and the buttons have been moved to the right (the fact that they have been moved from the left to the right after decades being on the left is irritating AF, but it's irrelevant here). So now the buttons, while still at the horizintal edge of the screen, are no longer at the corner of the screen, so when you "shoot" the mouse pointer to go to their area, you cannot simply go as far as you can and then click, you have to move a little bit down from the top in order to click the buttons. It's not just an aesthetic thing, it's a huge usablility thing. And it's not just a matter of habits and getting used to, it's objectively a step backwards (actually, it's a step in a completely new dimension, one of stupidity). It violates a very well known UI design principle that has been established for decades - and for a good reason, not just for historical reasons. Please revert this madness. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 22:32:12 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 4.15.0-109-generic, x86_64: installed nvidia-340, 340.108, 4.4.0-185-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer
[Desktop-packages] [Bug 1887254] [NEW] The new design makes maximized windows unusable
Public bug reported: I have just upgraded from ubuntu 16.04 to 18.04 (and I would have upgraded to 20.04 already if the stupid package manager weren't unable to resolve some conflicts which are "holding back" packages). An unbelievavly stupid mistake was made in the new design of windows. When you maximize a window, the title bar used to be at the very top of the screen, and the close/minimize/restore buttons used to be at the top-left corner of the screen. That means they had a property that in interface design has even a name, "infinite width" or "infinite something", that is: you can move the mouse all the way to the top and all the way to the left without having to "stop at the right time" in order to "land" within the area of the button, because the screen edges limit the mouse cursor. Now, the title bar of the window is no longer at the very top of the screen. At the top of the screen is a system bar. I mean that was already there, but the window buttons used to be in it on the left, as if the system bar at the top of the screen *was* the window title bar. Now the window title bar is just below it, and the buttons have been moved to the right (the fact that they have been moved from the left to the right after decades being on the left is irritating AF, but it's irrelevant here). So now the buttons, while still at the horizintal edge of the screen, are no longer at the corner of the screen, so when you "shoot" the mouse pointer to go to their area, you cannot simply go as far as you can and then click, you have to move a little bit down from the top in order to click the buttons. It's not just an aesthetic thing, it's a huge usablility thing. And it's not just a matter of habits and getting used to, it's objectively a step backwards (actually, it's a step in a completely new dimension, one of stupidity). It violates a very well known UI design principle that has been established for decades - and for a good reason, not just for historical reasons. Please revert this madness. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 22:32:12 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 4.15.0-109-generic, x86_64: installed nvidia-340, 340.108, 4.4.0-185-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
[Desktop-packages] [Bug 1887240] Re: screenshot no longer lets me copy before/without saving, nor choose where to save, if done via keyboard shortcut
Actually I see that half of the screenshots *were* lost (unless they were saved to some other random location that I have no way of knowing). So half of the time gnome-screenshot actually was not working (which could be partially expected during an upgrade while some of the system has been upgraded and some hasn't - but then I should have been shown a error message), and half of the time it was silently saving the screenshots to the default directory; and I couldn't even tell the difference. Unbelievable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1887240 Title: screenshot no longer lets me copy before/without saving, nor choose where to save, if done via keyboard shortcut Status in gnome-screenshot package in Ubuntu: New Bug description: I just upgraded from 16.04 to 18.04, and unsuprsisingly, in 1 minute of use I have already found out a backwards idiotic design decision in Gnome that degrades usability (but I bet they did it thinking it was an improvement). I was used to using gnome-screenshot as follows: - I use either the shift+PrintScreen shortcut to grab a rectangle, or (less frequently) just the PrintScreen key to capture the whole screen - then the popup would show up where I could either copy the screenshot to the clipboard, to paste it into Gimp or Telegram, or any other application accepting image input (and often not save the screenshot at all); or choose a destination to save the screenshot to, which almost never was the default. Now, after upgrading, I took (or wanted to take) a bunch of screenshots illustrating some of the pathetic bugs of the disastrous upgrade process, but to my surprise, even though I could hear the sound effect and see the visual effect of the screenshot being taken, no popup would show up. I thought gnome-screenshot was just broken and crashing like half of Ubuntu, and that none of the screenshot had been taken. Later it occurred to me to look at the default destination directory ~/Pictures, and it turned out all the screenshots are silently saved there. So now, if I take a screenshot using the keyboard shortcuts, I can neither: - copy the screenshot to the clipboard and omit saving it; nor: - choose to save it somewhere else other than the default. To do that, I have to launch the application manually. I have a launcher icon, but still I need two clicks to do what I would normally do with a single keyboard shortcut. I can unserstand that to some people, who just usually save their screenshots to the default location, this can be handy. But then it should be an option. I can't find a Settings menu or button or anything where I can change this behavior to restore the old one. Actually I can't even find a way to change the default save destination, which is additionally ridiculous. If such settings exist, they are undiscoverable. Additionally, even if this was just a change in default behavior (and hence configurable), the fact that the change happened silently is an additional serious issue. Given that the behavior changed, the first time I took a screenshot (via keyboard shortcut) with the new version, it should have shown a message saying "The screenshot was saved to /path/to/saved/screenshot [Don't show again]". That's how you change the behavior of things. You don't do it silently leaving me to wonder whether the screenshot was saved at all. Between the time I got the impressions screenshots were not working, and the time it occurred to me to look in the default directory and found out, I stopped taking screenshot. As usual, the Gnome team puts no thought whatsoever into what they do. They just keep making the software worse. I'm reporting this only to let you know, because as soon as I'm finished upgrading to the latest version just to give it a shot, I'm pretty sure I'll wipe out my hard disk and install OpenSUSE. I'm sick of Ubuntu. By the way, the reason I waited 4 years before upgrading, is mainly (1) because a single regression (which again is actually a design decision by Gnome, but also failure on the side of Ubuntu to patch it) that renders Nautilus (a basic component) completely unusable, which is https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1164016. And to a lesser extent (2) the fact that EVERY SINGLE distribution upgrade until now had always led to bricking my computer (furtunately not this time, it's just the ugly unusable mess that Ubuntu 18.10 is). So I always postpone dist upgrades to when I have a few spare hours to waste fixing things and getting my computer back to work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screenshot 3.25.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64
[Desktop-packages] [Bug 1887240] [NEW] screenshot no longer lets me copy before/without saving, nor choose where to save, if done via keyboard shortcut
Public bug reported: I just upgraded from 16.04 to 18.04, and unsuprsisingly, in 1 minute of use I have already found out a backwards idiotic design decision in Gnome that degrades usability (but I bet they did it thinking it was an improvement). I was used to using gnome-screenshot as follows: - I use either the shift+PrintScreen shortcut to grab a rectangle, or (less frequently) just the PrintScreen key to capture the whole screen - then the popup would show up where I could either copy the screenshot to the clipboard, to paste it into Gimp or Telegram, or any other application accepting image input (and often not save the screenshot at all); or choose a destination to save the screenshot to, which almost never was the default. Now, after upgrading, I took (or wanted to take) a bunch of screenshots illustrating some of the pathetic bugs of the disastrous upgrade process, but to my surprise, even though I could hear the sound effect and see the visual effect of the screenshot being taken, no popup would show up. I thought gnome-screenshot was just broken and crashing like half of Ubuntu, and that none of the screenshot had been taken. Later it occurred to me to look at the default destination directory ~/Pictures, and it turned out all the screenshots are silently saved there. So now, if I take a screenshot using the keyboard shortcuts, I can neither: - copy the screenshot to the clipboard and omit saving it; nor: - choose to save it somewhere else other than the default. To do that, I have to launch the application manually. I have a launcher icon, but still I need two clicks to do what I would normally do with a single keyboard shortcut. I can unserstand that to some people, who just usually save their screenshots to the default location, this can be handy. But then it should be an option. I can't find a Settings menu or button or anything where I can change this behavior to restore the old one. Actually I can't even find a way to change the default save destination, which is additionally ridiculous. If such settings exist, they are undiscoverable. Additionally, even if this was just a change in default behavior (and hence configurable), the fact that the change happened silently is an additional serious issue. Given that the behavior changed, the first time I took a screenshot (via keyboard shortcut) with the new version, it should have shown a message saying "The screenshot was saved to /path/to/saved/screenshot [Don't show again]". That's how you change the behavior of things. You don't do it silently leaving me to wonder whether the screenshot was saved at all. Between the time I got the impressions screenshots were not working, and the time it occurred to me to look in the default directory and found out, I stopped taking screenshot. As usual, the Gnome team puts no thought whatsoever into what they do. They just keep making the software worse. I'm reporting this only to let you know, because as soon as I'm finished upgrading to the latest version just to give it a shot, I'm pretty sure I'll wipe out my hard disk and install OpenSUSE. I'm sick of Ubuntu. By the way, the reason I waited 4 years before upgrading, is mainly (1) because a single regression (which again is actually a design decision by Gnome, but also failure on the side of Ubuntu to patch it) that renders Nautilus (a basic component) completely unusable, which is https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1164016. And to a lesser extent (2) the fact that EVERY SINGLE distribution upgrade until now had always led to bricking my computer (furtunately not this time, it's just the ugly unusable mess that Ubuntu 18.10 is). So I always postpone dist upgrades to when I have a few spare hours to waste fixing things and getting my computer back to work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-screenshot 3.25.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 18:56:58 2020 InstallationDate: Installed on 2013-10-11 (2464 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1887240 Title: screenshot no longer lets me copy before/without saving, nor choose where to save, if done via keyboard shortcut Status in gnome-screenshot package in Ubuntu: New Bug description: I just upgraded from 16.04 to 18.04, and unsuprsisingly, in 1 minute of use I
[Desktop-packages] [Bug 1886333] Re: Nautilus goes berserk when trying to switch to list view in Trash
Oh, here's another quirk: When I click the Trash icon in Nautilus, Nautilus's Launcher icon immediately disappears, even though its window doesn't. It happened me a few times and each time I thought I had closed the window and forgotten, but then I realised, by minimizing all other windows one by one, that several Nautilus windows were still there. Pathetic. And this isn't just a bug in Nautilus (I'm sure the main triggering reason is a bug in nautilus), it's also a bug in whoever is responsible for managing windows (Xorg? Compiz? I have no idea), because it should never allow to hide a launcher icon for a window that remains open. That's an inconsistent situation that should just be forbidden at the deepest level. The whole thing is such a fucking mess. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1886333 Title: Nautilus goes berserk when trying to switch to list view in Trash Status in nautilus package in Ubuntu: New Bug description: Steps to reproduce: 1. open Nautilus 2. Select icons view 3. open Trash 4. try to switch to list view by clicking on the button on the top right Expected: should immediately switch to list mode. There's no acceptable valid reason for this to be slow. But if, for whatever valid reason, it did require a perceivable amount of time (which btw is an assumtion you should always make when designing the UI, because even a few milliseconds can be perceivable enough that visual feedback needs to be given and interaction can happen meanwhile), you should see a spinning icon somewhere giving you visual feedback that something is being processed (and you should be able to instantly go back to icons mode) Observed: it remains in icons mode as if you hadn't clicked anything (despite the fact that the list mode button becomes apparently selected). I have no idea whether it simply ignores you and doesn't switch to list mode without any error message, or if it's actually processing and taking long because Nautilus sucks and is slow and inefficient, but gives no visual feedback that it's processing something. But it doesn't end here: 4. Close Nautilus and open it again 5. Switch to list mode BEFORE you open trash (succesfully switches) 6. Open Trash => Now the Trash appears empty, even though it's not. Again, no idea whether it's loading and taking long: there's no indication of it. 7. Try to switch back to icon mode: => goes back to the folder you were browsing before, and does switch to icons mode. It's all a fucking mess - something is way slower than it should - the UI seems to be designed around the (never correct and in this case false) assumption that everything happens instantly, so there's no feedback when you need to wait because something is being loaded, and when that happens and you keep doing stuff, the behavior becomes inconsistent and everything goes completely berserk. This is fucking pathetic. And don't start with "You are using an old version of Ubuntu bla bla bla". I am using an old version because of an unrelated disgraceful regression in Nautilus itself which renders it completely unusable from Ubuntu 17.04 onward ana that to this day hasn't been fixed, of which luckily enough I became aware before I upgraded, so I stuck with 16.04. Furthermore, 16.04 is LTS and hasn't reached EOL yet, so bugs that render the system completely unusable like this one have to be fixed and the fix has to be released to 16.04. Anyway I don't give a fuck. I'm sick of Ubuntu and I'm switching to OpenSuse soon. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 Uname: Linux 4.4.0-184-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 5 18:42:26 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1161x849+533+136'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2458 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1886333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1886333] [NEW] Nautilus goes berserk when trying to switch to list view in Trash
Public bug reported: Steps to reproduce: 1. open Nautilus 2. Select icons view 3. open Trash 4. try to switch to list view by clicking on the button on the top right Expected: should immediately switch to list mode. There's no acceptable valid reason for this to be slow. But if, for whatever valid reason, it did require a perceivable amount of time (which btw is an assumtion you should always make when designing the UI, because even a few milliseconds can be perceivable enough that visual feedback needs to be given and interaction can happen meanwhile), you should see a spinning icon somewhere giving you visual feedback that something is being processed (and you should be able to instantly go back to icons mode) Observed: it remains in icons mode as if you hadn't clicked anything (despite the fact that the list mode button becomes apparently selected). I have no idea whether it simply ignores you and doesn't switch to list mode without any error message, or if it's actually processing and taking long because Nautilus sucks and is slow and inefficient, but gives no visual feedback that it's processing something. But it doesn't end here: 4. Close Nautilus and open it again 5. Switch to list mode BEFORE you open trash (succesfully switches) 6. Open Trash => Now the Trash appears empty, even though it's not. Again, no idea whether it's loading and taking long: there's no indication of it. 7. Try to switch back to icon mode: => goes back to the folder you were browsing before, and does switch to icons mode. It's all a fucking mess - something is way slower than it should - the UI seems to be designed around the (never correct and in this case false) assumption that everything happens instantly, so there's no feedback when you need to wait because something is being loaded, and when that happens and you keep doing stuff, the behavior becomes inconsistent and everything goes completely berserk. This is fucking pathetic. And don't start with "You are using an old version of Ubuntu bla bla bla". I am using an old version because of an unrelated disgraceful regression in Nautilus itself which renders it completely unusable from Ubuntu 17.04 onward ana that to this day hasn't been fixed, of which luckily enough I became aware before I upgraded, so I stuck with 16.04. Furthermore, 16.04 is LTS and hasn't reached EOL yet, so bugs that render the system completely unusable like this one have to be fixed and the fix has to be released to 16.04. Anyway I don't give a fuck. I'm sick of Ubuntu and I'm switching to OpenSuse soon. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 Uname: Linux 4.4.0-184-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 5 18:42:26 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1161x849+533+136'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2458 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial ** Description changed: Steps to reproduce: 1. open Nautilus 2. Select icons view 3. open Trash 4. try to switch to list view by clicking on the button on the top right Expected: should immediately switch to list mode. There's no acceptable valid reason for this to be slow, since it is possible to make it efficient enough to make it quick. If, for whatever valid reason, it did - require a perceivable amount of time, you should see a spinning icon - somewhere giving you visual feedback that something is being processed - (and you should be able to instantly go back to icons mode) + require a perceivable amount of time (which btw is an assumtion you + should always make when designing the UI, because even a few + milliseconds can be perceivable enough that visual feedback needs to be + given and interaction can happen meanwhile), you should see a spinning + icon somewhere giving you visual feedback that something is being + processed (and you should be able to instantly go back to icons mode) Observed: it remains in icons mode as if you hadn't clicked anything (despite the fact that the list mode button becomes apparently selected). I have no idea whether it simply ignores you and doesn't switch to list mode without any error message, or if it's actually processing and taking long
[Desktop-packages] [Bug 1886329] Re: The thing that opens by double-clicking on a .deb file never works
** Summary changed: - The crap that opens by double-clicking on a .deb file never works + The thing that opens by double-clicking on a .deb file never works -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1886329 Title: The thing that opens by double-clicking on a .deb file never works Status in gnome-software package in Ubuntu: New Bug description: I downloaded a .deb file. It was Virtual Box, but that is not relevant, nor is whether there was something wrong with that .deb file or whether my system was properly set up to be ready to install that package or not. I double-clicked on the .deb file from within a folder in Nautilus, and a program opened that if I'm not mistaken is called Ubuntu Software Center, or something like that. That showed a list with only one item that corresponded to the file I had opened: Virtual Box Whatever, with a title and a description of the package, and there was an "Install" button. I clicked the Install button. Expected: either install the package succesfully, or give me an error message telling me exactly why you can't install it. These are the two only possible expected outcomes; no other outcome is acceptable. Observed: First, when I clicked on Install, something showed up for a very brief time; maybe a progress bar or something. Then that went away, and the Install button was visible again. This already makes no sense. I clicked install, so either you are able to install or you are not. If you are not, you should be showing me an error message, and the Install button should no longer be called "Install" but either not be there or be called "try again" (unless if you first show me an error message and I dismiss it, then we may be back to square one). If you are able to install, then you should be installing it, and if you are, I should be seeing an indication of the status and progress of the installation. So either the installation silently failed and no error message was shown, which is not acceptable, or the installation was ongoing somewhere in the background, or being prepared for, and there was no indication of it. Then I clicked "Install" again. This time, an icon appeared in the Launcher with something that looked like an empty or almost empty progress bar (i.e. a progress bar at its very beginning). When a new icon shows up in the Launcher, a new window should ALWAYS be open. The very thing an icon in the Launcher represents is a window. But no. No window or popup showed up when the Launcher icon showed up, and clicking on it did nothing. By right-clicking on it there was no "quit" option either. So the launcher icon was probably some process that wasn't responding. First: if you launched a process that is not responding, something is broken. Secondly, you should detect it, show an error message, and allow me to take action. You don't just leave me with a stuck hung process and a Launcher icon that doesn't even allow me to figure out what the hung process is and to abort it. This is not the first time this happens to me. It has happened almost every time I've ever tried to install a .deb file by double-clicking on it (which is not something I do often). It doesn't matter whether the .deb file I'm trying to install is broken, or cannot be installed for any valid reason: if that is the case you tell me what that fucking reason it and show me an error message, with all the details and the options. NOTE: after all this, I restarted my system, and then I went to the folder containing the .deb file and ran: sudo apt install ./that_file.deb and that installed Virtual Box succesfully and seamlessly. All I was expecting the Ubuntu Software Center (or whatever that thing is called) to do by double clicking on the .deb file was the same thing I did by running that command from the terminal. The only reason I didn't do it from the terminal was to not have to google what the command was. That's why you are allowed to double-click on things, so the system takes care to do whatever it needs to be done for you. It's pathetic that by double clicking on a .deb file the system isn't able to install a package that I can seamlessly install with a one- line command that required no interaction (besides one single prompt "are you sure Y/N") and had no error. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-software 3.20.5-0ubuntu0.16.04.13 ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 Uname: Linux 4.4.0-184-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 5 17:26:39 2020 InstallationDate: Installed on 2013-10-11 (2458 days ago) InstallationMedia: Ubuntu 13.04 "Raring
[Desktop-packages] [Bug 1886329] [NEW] The crap that opens by double-clicking on a .deb file never works
Public bug reported: I downloaded a .deb file. It was Virtual Box, but that is not relevant, nor is whether there was something wrong with that .deb file or whether my system was properly set up to be ready to install that package or not. I double-clicked on the .deb file from within a folder in Nautilus, and a program opened that if I'm not mistaken is called Ubuntu Software Center, or something like that. That showed a list with only one item that corresponded to the file I had opened: Virtual Box Whatever, with a title and a description of the package, and there was an "Install" button. I clicked the Install button. Expected: either install the package succesfully, or give me an error message telling me exactly why you can't install it. These are the two only possible expected outcomes; no other outcome is acceptable. Observed: First, when I clicked on Install, something showed up for a very brief time; maybe a progress bar or something. Then that went away, and the Install button was visible again. This already makes no sense. I clicked install, so either you are able to install or you are not. If you are not, you should be showing me an error message, and the Install button should no longer be called "Install" but either not be there or be called "try again" (unless if you first show me an error message and I dismiss it, then we may be back to square one). If you are able to install, then you should be installing it, and if you are, I should be seeing an indication of the status and progress of the installation. So either the installation silently failed and no error message was shown, which is not acceptable, or the installation was ongoing somewhere in the background, or being prepared for, and there was no indication of it. Then I clicked "Install" again. This time, an icon appeared in the Launcher with something that looked like an empty or almost empty progress bar (i.e. a progress bar at its very beginning). When a new icon shows up in the Launcher, a new window should ALWAYS be open. The very thing an icon in the Launcher represents is a window. But no. No window or popup showed up when the Launcher icon showed up, and clicking on it did nothing. By right-clicking on it there was no "quit" option either. So the launcher icon was probably some process that wasn't responding. First: if you launched a process that is not responding, something is broken. Secondly, you should detect it, show an error message, and allow me to take action. You don't just leave me with a stuck hung process and a Launcher icon that doesn't even allow me to figure out what the hung process is and to abort it. This is not the first time this happens to me. It has happened almost every time I've ever tried to install a .deb file by double-clicking on it (which is not something I do often). It doesn't matter whether the .deb file I'm trying to install is broken, or cannot be installed for any valid reason: if that is the case you tell me what that fucking reason it and show me an error message, with all the details and the options. NOTE: after all this, I restarted my system, and then I went to the folder containing the .deb file and ran: sudo apt install ./that_file.deb and that installed Virtual Box succesfully and seamlessly. All I was expecting the Ubuntu Software Center (or whatever that thing is called) to do by double clicking on the .deb file was the same thing I did by running that command from the terminal. The only reason I didn't do it from the terminal was to not have to google what the command was. That's why you are allowed to double-click on things, so the system takes care to do whatever it needs to be done for you. It's pathetic that by double clicking on a .deb file the system isn't able to install a package that I can seamlessly install with a one-line command that required no interaction (besides one single prompt "are you sure Y/N") and had no error. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-software 3.20.5-0ubuntu0.16.04.13 ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 Uname: Linux 4.4.0-184-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 5 17:26:39 2020 InstallationDate: Installed on 2013-10-11 (2458 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1886329 Title: The crap that opens by double-clicking on a .deb file never works Status in gnome-software package in Ubuntu: New Bug description: I
[Desktop-packages] [Bug 1885435] [NEW] The wrong sequence of mouse events can render the whole system unusable
Public bug reported: This is 100% reproducible with any window, I'll use a terminal window as an example. Steps to reproduce: - open a terminal window (again, this could be a Gedit, Nautilus window or any other window) - make sure the window is not maximized - Place the mouse cursor at the center of the right border of the window, press the mouse left button and don't release it, so as to resize the window by dragging its right border - While dragging the terminal window's right border, press and hold the mouse right button too (remember you're still holding the left button too) - While still holding both mouse buttons pressed, move the mouse cursor away from the border of the window fast. If you move it fast enough, at some point the border will stop following the mouse cursor (which wouldn't happen if you hadn't pressed both buttons). - While the mouse cursor is outside the terminal winow, release the right button and then the left button. Now you are no longer holding any mouse button pressed - move the mouse cursor to the left and to right "crossing" the terminal window border, that is, move the mouse inside and outside the terminal window. Notice how, whenever the cursor "crosses" the window's right border, the border nonsensically moves a little bit following the movements of the cursor for a fraction of a second, as if you were still dragging it, but then it stops following the cursor. This is the first sign that something has gone completely berserk, but it's still nothing compared to what is coming - while the mouse cursor is outside of the offending window (i.e. the terminal window in our example), click on something outside of it. For example, in my case that's a maximized Chrome window that's behind. Observed disaster: now you are unable to do anything with the mouse. Try clicking on any window to move, close, or resize it. Try to click on stuff to give it focus. Try to click on Launcher icons. None of this has any effect. It's as if your mouse buttons dead. Not even by trying to go back to the original window and press and release the mouse buttons in any particular order while the cursor is over the window border seems to allow you to "unlock" the system. There's no way to recover from this situation except by KILLING the offending window without using the mouse. For example, by using alt+tab as many time as needed to give it focus, and then, since in this case it is a terminal, typing "exit" and hitting Enter, so the window gets closed and normal functioning of the mouse gets restored. If the offending window is not a terminal window, then you can hit Ctrl+Alt+T to open a new terminal, and then use a "kill" or "killall" command to kill the process that owns the offending window. Both of these imply loss of any unsaved work. This is a fucking disaster and an incredibly stupid bug of the kind that you usually observe in "software" written by novice programmers (or rather, non-programmers such as web designers playing around with javascript) who write their first programs with mouse events (press, release, rollover, etc) and forget to take into account all possible sequences of events. Seriously, I hadn't seen such stupid mouse behavior bugs outside of the scope of amateur website UIs. Fucking unbelievable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Jun 28 17:28:05 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2451 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-179-generic
[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
No I can't. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Confirmed Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
I think this was fixed upstream like four years ago: https://bugzilla.gnome.org/show_bug.cgi?id=763600 ** Bug watch added: bugzilla.gnome.org/ #763600 https://bugzilla.gnome.org/show_bug.cgi?id=763600 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Confirmed Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883000] Re: screengrab window remain open, without icon in launcher, hence impossible to find
> Do you click on the dialog button on the decoration X ? Sometimes that, sometimes I hit the Esc key. Actually I cannot tell with 100% certainty that the window fails to close when I do so. It may be that I failed/forgot to close it, and that the real issue is the launcher not listing it. However, this only happens to me when I take several screenshots (not many, because of bug 1526082), and accumulate a few gnome-screenshot windows open, and then go to close them all. I never, ever observed taking a single screenshot and the launcher icon not appearing since the beginning. Nor taking a single screenshot, then attempting to close the single window and observing the issue. It's only when I have a few open and finally close them all, that after closing what seems to be the last one, there's one more left with no launcher icon (just to clarify: not always, only very rarely). So it's like the count of open windows gets the wrong value at some point, either when opening a new instance or when closing one. I don't think I've ever observed this with other applications, though that might be because gnome-screenshot is the only one of which I so often open a few instances. The only other two I can think of are the terminal and nautilus, and I don't think I've observed this with those. Might be just statistics. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1883000 Title: screengrab window remain open, without icon in launcher, hence impossible to find Status in gnome-screenshot package in Ubuntu: New Bug description: Sometimes, after taking a screenshot, when you click to close the gnome-screenshot window, it fails to close and remains open, but in the background, behind everything else. What is much worse, is that the icon in launcher does disappear. So, you have a "ghost" window left open, behind every other window, that you have NO WAY TO REACH except by minimizing or closing EVERY SINGLE other window one by one, until the only one that remains is screengrab. This makes bug 1526082 even more annoying, as sometimes, even after you (think you) have closed all screengrab's windows, there is still a rectanguar area of the screen that is slightly dimmed. The first time it happened to me, I thought bug 1526082 had got worse and that the screengrabbed area would now remain dimmed forever even after closing screengrab. But then I found out the window was still there. This is fucking pathetic. Please drop Gnome for good and pick an alternative that is decently maintained, by non-idiots. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: screengrab (not installed) ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 10 19:54:46 2020 InstallationDate: Installed on 2013-10-11 (2434 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: screengrab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1883000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883000] Re: screengrab window remain open, without icon in launcher, hence impossible to find
Hopefully gnome-screenshot is the right package -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1883000 Title: screengrab window remain open, without icon in launcher, hence impossible to find Status in gnome-screenshot package in Ubuntu: New Bug description: Sometimes, after taking a screenshot, when you click to close the gnome-screenshot window, it fails to close and remains open, but in the background, behind everything else. What is much worse, is that the icon in launcher does disappear. So, you have a "ghost" window left open, behind every other window, that you have NO WAY TO REACH except by minimizing or closing EVERY SINGLE other window one by one, until the only one that remains is screengrab. This makes bug 1526082 even more annoying, as sometimes, even after you (think you) have closed all screengrab's windows, there is still a rectanguar area of the screen that is slightly dimmed. The first time it happened to me, I thought bug 1526082 had got worse and that the screengrabbed area would now remain dimmed forever even after closing screengrab. But then I found out the window was still there. This is fucking pathetic. Please drop Gnome for good and pick an alternative that is decently maintained, by non-idiots. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: screengrab (not installed) ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 10 19:54:46 2020 InstallationDate: Installed on 2013-10-11 (2434 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: screengrab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1883000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883000] Re: screengrab window remain open, without icon in launcher, hence impossible to find
I guess I marked the wrong package, as Ubuntu doesn't provide any easy mechanism for the end user to figure out which fucking package a given application belongs to, so one has to guess. I am using standard Ubuntu 16.04, not Lubuntu, and this is about the default screenshot grabber that appears as "Screenshot" and that is launched by pressing the PrintScreen key. I think the executable is /usr/bin/gnome-screenshot ** Package changed: screengrab (Ubuntu) => gnome-screenshot (Ubuntu) ** Changed in: gnome-screenshot (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1883000 Title: screengrab window remain open, without icon in launcher, hence impossible to find Status in gnome-screenshot package in Ubuntu: New Bug description: Sometimes, after taking a screenshot, when you click to close the gnome-screenshot window, it fails to close and remains open, but in the background, behind everything else. What is much worse, is that the icon in launcher does disappear. So, you have a "ghost" window left open, behind every other window, that you have NO WAY TO REACH except by minimizing or closing EVERY SINGLE other window one by one, until the only one that remains is screengrab. This makes bug 1526082 even more annoying, as sometimes, even after you (think you) have closed all screengrab's windows, there is still a rectanguar area of the screen that is slightly dimmed. The first time it happened to me, I thought bug 1526082 had got worse and that the screengrabbed area would now remain dimmed forever even after closing screengrab. But then I found out the window was still there. This is fucking pathetic. Please drop Gnome for good and pick an alternative that is decently maintained, by non-idiots. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: screengrab (not installed) ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 10 19:54:46 2020 InstallationDate: Installed on 2013-10-11 (2434 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: screengrab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1883000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526082] Re: Area of screenshot remains highlighted until application closed
How long can it possibly take to fix this crap??? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1526082 Title: Area of screenshot remains highlighted until application closed Status in gnome-screenshot package in Ubuntu: Confirmed Bug description: Steps to reproduce: - hit shift+PrintScreen - Drag and drop to select a rectangular area of the screen to take a screenshot of - don't close the Gnome Screenshot dialog. Minimize it if you want Observed issue: the rectangular area that has been captured remains slightly highlighted (i.e. brighter) as long as the Gnome Screenshot application's dialog is open. No matter what window is on the foreground (or even fullscreen for that matter), you'll keep noticing the slightly brighter rectangle. See attachment screenshot: you can see the rectangle approximately at the center of the screen. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-screenshot 3.14.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-37.42-generic 3.19.8-ckt9 Uname: Linux 3.19.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 14 23:20:01 2015 InstallationDate: Installed on 2013-10-11 (794 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to vivid on 2015-08-15 (121 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1526082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
When this happens, it often also happens that a process whose name I can't remember right now but that has the word "trash" in it, consumes an awful lot of CPU during the time the flickering is observed (which is sometimes several minutes). FIX THE FUCKING IMPORTANCE. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Confirmed Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
> Reporting upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/ would be more useful than arguing over bug settings on this ticket... In my experience, reporting anything upstream to GNOME is a fucking waste of time. Gnome developers have proven to be a bunch of idiots. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Confirmed Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882362] Re: Focus not where it should be
Importance low??? Have you fucking read the report? This can cause you to ACCIDENTALLY DELETE stuff. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1882362 Title: Focus not where it should be Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce: 0. Make sure you have an image file in your desktop, and that you have a folder somewhere in your filesystem that contains at least one file of any kind. Make also sure you have no window open, or otherwise do Show Desktop so that your desktop is visible. 1. Open a nautilus window and navigate to the a folder that has some files in it. So now a Nautilus window is in foreground with a folder open showing the contents of the folder 2. Make sure this window is not maximized, and move it around so that, on the background, you can see your desktop, and specifically, an image file that is in your desktop. Remember, at this stage the Nautilus window with the folder is in the foreground, focused. 3. Click on some file within the nautilus window to select it. 4. Click on the desktop background. Then click on some file on the desktop. Then on another one. Then finally on one particular image file that you have in your desktop. Now the desktop has focus and something in it is selected. NOTE: you can skip step 4, and you would observe the issue allthesame and it would still be bad. But the fact that explicitly including this step 4 you can observe the issue, makes it even more egregious. 5. Double ckick on the image file in the desktop, so as to open it in the default image viewer Now the image viewer window is in the foreground. 6. Close the image viewer window 7. Hit the Delete key. ** EXPECTED ** After step 6, focus should return to the desktop, where the image file was selected. Hence, hitting the Delete key should delete it ** OBSERVED ** For some random nonsensical reason, after step 6, the Nautilus window with the folder is focused, and hence, when you hit the delete key you delete whatever file was selected in it. This is a HUGE issue which may cause you to delete the wrong content without even realising it. And if you don't realise soon enough, you may be unable to undelete it. Just one more of a gazillion bugs that make Nautilus not only unusable, but also DANGEROUS. One of the most essential components of a Desktop operating system and yet one of the most broken ones. Fucking pathetic. I'm done with this crap, I will get rid of Ubuntu and install some other distro. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 6 15:45:50 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1464x887+768+660'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2429 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882362] [NEW] Focus not where it should be
Public bug reported: Steps to reproduce: 0. Make sure you have an image file in your desktop, and that you have a folder somewhere in your filesystem that contains at least one file of any kind. Make also sure you have no window open, or otherwise do Show Desktop so that your desktop is visible. 1. Open a nautilus window and navigate to the a folder that has some files in it. So now a Nautilus window is in foreground with a folder open showing the contents of the folder 2. Make sure this window is not maximized, and move it around so that, on the background, you can see your desktop, and specifically, an image file that is in your desktop. Remember, at this stage the Nautilus window with the folder is in the foreground, focused. 3. Click on some file within the nautilus window to select it. 4. Click on the desktop background. Then click on some file on the desktop. Then on another one. Then finally on one particular image file that you have in your desktop. Now the desktop has focus and something in it is selected. NOTE: you can skip step 4, and you would observe the issue allthesame and it would still be bad. But the fact that explicitly including this step 4 you can observe the issue, makes it even more egregious. 5. Double ckick on the image file in the desktop, so as to open it in the default image viewer Now the image viewer window is in the foreground. 6. Close the image viewer window 7. Hit the Delete key. ** EXPECTED ** After step 6, focus should return to the desktop, where the image file was selected. Hence, hitting the Delete key should delete it ** OBSERVED ** For some random nonsensical reason, after step 6, the Nautilus window with the folder is focused, and hence, when you hit the delete key you delete whatever file was selected in it. This is a HUGE issue which may cause you to delete the wrong content without even realising it. And if you don't realise soon enough, you may be unable to undelete it. Just one more of a gazillion bugs that make Nautilus not only unusable, but also DANGEROUS. One of the most essential components of a Desktop operating system and yet one of the most broken ones. Fucking pathetic. I'm done with this crap, I will get rid of Ubuntu and install some other distro. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 6 15:45:50 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1464x887+768+660'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2429 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial ** Description changed: Steps to reproduce: 0. Make sure you have an image file in your desktop, and that you have a - folder somewhere that contains at least one file of any kind. Make also - sure you have no window open, or otherwise do Show Desktop so that your - desktop is visible. + folder somewhere in your filesystem that contains at least one file of + any kind. Make also sure you have no window open, or otherwise do Show + Desktop so that your desktop is visible. 1. Open a nautilus window and navigate to the a folder that has some files in it. So now a Nautilus window is in foreground with a folder open showing the contents of the folder 2. Make sure this window is not maximized, and move it around so that, on the background, you can see your desktop, and specifically, an image file that is in your desktop. Remember, at this stage the Nautilus window with the folder is in the foreground, focused. 3. Click on some file within the nautilus window to select it. 4. Click on the desktop. Then click on some file on the desktop. Then on another one. Then finally on one particular image file that you have in your desktop. Now the desktop has focus and something in it is selected. NOTE: you can skip step 4, and you would observe the issue allthesame and it would still be bad. But the fact that explicitly including this step 4 you can observe the issue, makes it even more egregious. 5. Double ckick on the image file in the desktop, so as to open it in the default image viewer Now the image viewer window is in the foreground. 6. Close the image viewer window - 7.
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
Actually this one is marked as fixed because it was indeed fixed several years ago, but then the fix was lost (i.e. the patch not rewritten) when a new version of gnome was released, "because" search is faster now, which according to some nonsensical reasoning by those who don't uderstand this issue, meant to them that the issue was no longer relevant. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879343] [NEW] REGRESSION - Ctrl+Alt+F1 no longer gives me access to virtual terminal, just a black screen
Public bug reported: Ctrl+Alt+F1 used to give you access to a cirtual terminal, or virtual console, not entirely sure what that's called, where you can log in into a shell and run commands. I use that when some of the tons of bugs in Ubuntu makes the system hang so badly that I can't even open a terminal window, in order to figure out if there's a process that I can kill. Then I'd be able to return to the xorg screen with Ctrl+Alt+F7. Now (and even while the system is not hung at all) I'm doing ctrl+Alt+F1, and all I get is a black screen with no console/terminal at all. Completely fucking useless, ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon May 18 17:02:03 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2410 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-173-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Apr 17 02:39:40 2020 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879343 Title: REGRESSION - Ctrl+Alt+F1 no longer gives me access to virtual terminal, just a black screen Status in xorg package in Ubuntu: New Bug description: Ctrl+Alt+F1 used to give you access to a cirtual terminal, or virtual console, not entirely sure what that's called, where you can log in into a shell and run commands. I use that when some of the tons of bugs in Ubuntu makes the system hang so badly that I can't even open a terminal window, in order to figure out if there's a process that I can kill. Then I'd be able to return to the xorg screen with Ctrl+Alt+F7. Now (and even while the system is not hung at all) I'm doing ctrl+Alt+F1, and all I get is a black screen with no console/terminal at all. Completely fucking useless, ProblemType: Bug DistroRelease: Ubuntu
[Desktop-packages] [Bug 1879169] [NEW] Thumbs never updated after renaming a bunch of image files
Public bug reported: I refuse to waste my time reporting this upstream, since Gnome developers (or at least Nautilus developers) have proven in several occasions to be a bunch of idiots unable to deal with bug reports (or with bugs in general). You deal with them. I had a folder containing a bunch of image files, namely .png files, named 1.png, 2.png up to 100.png and more. I deleted many of them and then renamed the remaining ones to 1.png through 21.png. Now I look at the folder and all the thumbs have not been updated. For example, the thumb of say 5.png is the thumb of the image that used to be called 5.png before renaming. Even hitting f5 does not rebuild the thumbs, and if I right-click on the folder I don't see any option in the context menu to manually force- rebuild the thumns (which shouldn't be necessary in the first place but should be something I'd be able to do). It's obvious that renaming files should invalidate the thumbs cache. Fucking pathetic. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 17 17:36:04 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1321x879+1501+562'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2409 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1879169 Title: Thumbs never updated after renaming a bunch of image files Status in nautilus package in Ubuntu: New Bug description: I refuse to waste my time reporting this upstream, since Gnome developers (or at least Nautilus developers) have proven in several occasions to be a bunch of idiots unable to deal with bug reports (or with bugs in general). You deal with them. I had a folder containing a bunch of image files, namely .png files, named 1.png, 2.png up to 100.png and more. I deleted many of them and then renamed the remaining ones to 1.png through 21.png. Now I look at the folder and all the thumbs have not been updated. For example, the thumb of say 5.png is the thumb of the image that used to be called 5.png before renaming. Even hitting f5 does not rebuild the thumbs, and if I right-click on the folder I don't see any option in the context menu to manually force-rebuild the thumns (which shouldn't be necessary in the first place but should be something I'd be able to do). It's obvious that renaming files should invalidate the thumbs cache. Fucking pathetic. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 17 17:36:04 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1321x879+1501+562'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2409 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1879169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 737615] Re: Can't save changes in "Edit Connections..." for Wi-Fi networks to which one doesn't have the password
** This bug is no longer a duplicate of bug 1409866 Will not find network after connection info is edited -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/737615 Title: Can't save changes in "Edit Connections..." for Wi-Fi networks to which one doesn't have the password Status in Linux: Unknown Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Debian: New Bug description: Binary package hint: network-manager Steps to reproduce: 1) Right-click on Network Manager's tray icon 2) select "edit connections" 3) go to the "wireless" tab 4) select any connection in the list, except the one you are currently connected to 5) Click "Edit" 5) Change some settings Expected: there should be some way to save those changes Observed: the "Apply" button is greyed out. There is no "Save" button. If you hit Cancel, obviously the changes are discarded. If you edit the network you are connected to, the Apply button works, but why on earth are'n you allowed to save changes to a network you are not connected to? And if there was a reason why you can't, then why are you allowed to edit in the first place? ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: network-manager 0.8-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-29.58-generic 2.6.32.28+drm33.13 Uname: Linux 2.6.32-29-generic i686 NonfreeKernelModules: nvidia Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Fri Mar 18 14:47:06 2011 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) IpRoute: 192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.105 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 192.168.2.1 dev wlan0 proto static Keyfiles: Error: [Errno 2] No such file or directory ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/737615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868158] Re: Reopen issue 1666681
> also that bug is a duplicate as you knew when opening it, the fact that the > issue has been > wontfixed is not a reason to create extra work for others by registered a new > ticket I can't reopen that one and comments seem to be ignored, that's why I created a new one. What you should do then is mark this one as duplicate and reopen the original one. Anyway, who cares, Ubuntu is beyond help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1868158 Title: Reopen issue 181 Status in nautilus package in Ubuntu: Won't Fix Bug description: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream developers defend) demonstrates that it's maintained by a bunch of idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. Anyway, in the shorter term, it seems that there are working patches available to mitigate this disgrace. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2351 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868158] Re: Reopen issue 1666681
* wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1868158 Title: Reopen issue 181 Status in nautilus package in Ubuntu: Confirmed Bug description: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream developers defend) demonstrates that it's maintained by a bunch of idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. Anyway, in the shorter term, it seems that there are working patches available to mitigate this disgrace. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2351 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868158] Re: Reopen issue 1666681
Ok, however, that's not a reason for marking this as "opinion". The issue had already been addressed so there's no question that the behavior is wrong and has to be fixed. That debate has been settled ages ago. Also the importance shouldn't be "whichlist". This makes Nautilus unusable. ** Changed in: nautilus (Ubuntu) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1868158 Title: Reopen issue 181 Status in nautilus package in Ubuntu: Confirmed Bug description: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream developers defend) demonstrates that it's maintained by a bunch of idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. Anyway, in the shorter term, it seems that there are working patches available to mitigate this disgrace. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2351 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868158] [NEW] Reopen issue 1666681
Public bug reported: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream developers defend) demonstrates that it's maintained by a bunch of idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. Anyway, in the shorter term, it seems that there are working patches available to mitigate this disgrace. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2351 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial ** Description changed: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream - developers defend) demonstrates that it's maintained by a bunch of - idiots. + developers defend) proves that Nautilus maintained by a bunch of idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: - b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' - b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" - b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' - b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" + b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' + b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" + b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' + b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2351 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream - developers defend) proves that Nautilus maintained by a bunch of idiots. + developers defend) demonstrates that it's maintained by a bunch of + idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. + + Anyway, in the shorter term, it seems that there are working patches + available to mitigate this disgrace. + ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state'
[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
Why the fuck was this closed??? See also the discussion on 1164016 after this idiocy resurfaced. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/181 Title: Restore interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Won't Fix Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
Please fix the importance. "Importance Low" is clearly wrong (as I pointed out almost a year ago). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Confirmed Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
Please fix the importance. And to the idiot who set this to low: stop setting the importance of bugs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Confirmed Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853707] Re: Whole system stopped responding because of single program's fault - no way out, had to force power off
What is suggested there is that something in the offending program (libreCAD) eats up all the RAM. What I am reporting here as a bug in the OS is the fact that the WHOLE SYSTEM hangs irrecoverably because of that. Quoting a comment from the above link: > Linux is very good managing the RAM memory, except when it ends without > memory. > Then the full system is frozen (Ubuntu, Debian, Arch and all the distros). > When this happens, it's impossible to open a terminal to kill the process. > You will have the same experience opening hundreds of browser tabs with Flash > Player, for example. If that is true it is a critical bug in Linux, which should be regarded as a huge vulnerability rather than something we just have to live with. Unless of course that is all incorrect and this is actually caused by a bug in the NVidia driver (again, no idea where you get that from): in that case of course, I guess the OS cannot be expected to be able to recover from some extremely bad behavior of a driver. It IS expected to be able to recover from the worst imaginable behavior of the most buggy and malicious program, but probably not of a driver which is in fact part of the OS itself. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1853707 Title: Whole system stopped responding because of single program's fault - no way out, had to force power off Status in compiz package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: What I did was: - install LibreCAD (by adding their ppa and then using apt-get) - open it - try to open the attached .dwf file LibreCAD hanged and the whole system stopped responding. The mouse button stopped moving, the system wouldn't respond to keyboard strokes, AND not even Ctrl+Alt+F1 worked to open a virtual terminal where I could have tried killing some process. Obviously there's a bug in LibreCAD, but no matter how badly a buggy (or even evil) process behaves, if a single misbehaving program can cause the whole OS to stall in a way that you cannot recover from, then by definition there's a bug in the OS. You must ALWAYS be able to kill the offending program and resume normal operation without having to stop one single application other than the offending one. I have no idea whether the bug is actually in Xorg or somewhere else; the reason I'm reporting it against xorg is that ctrl+alt+F1 wouldn't work. I might very well be wrong but I believe xorg is responsible for providing the virtual terminal via ctrl+alt+f1? Either way, that MUST ALWAYS be available no matter how badly things go. That a single program hanging causes me to have to force-power down the computer is outrageous. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Nov 23 17:27:22 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2233 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-169-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name:
[Desktop-packages] [Bug 1853707] Re: Whole system stopped responding because of single program's fault - no way out, had to force power off
Looked in /var/crash after this happened again (did I mention it's systematically reproducible?) and there's nothing there. I'm not sure what makes you think this has to do with NVidia drivers. This seems to suggest it doesn't: https://github.com/LibreCAD/LibreCAD/issues/1161#issuecomment-557833504 but I don't know. ** Bug watch added: github.com/LibreCAD/LibreCAD/issues #1161 https://github.com/LibreCAD/LibreCAD/issues/1161 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1853707 Title: Whole system stopped responding because of single program's fault - no way out, had to force power off Status in compiz package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: What I did was: - install LibreCAD (by adding their ppa and then using apt-get) - open it - try to open the attached .dwf file LibreCAD hanged and the whole system stopped responding. The mouse button stopped moving, the system wouldn't respond to keyboard strokes, AND not even Ctrl+Alt+F1 worked to open a virtual terminal where I could have tried killing some process. Obviously there's a bug in LibreCAD, but no matter how badly a buggy (or even evil) process behaves, if a single misbehaving program can cause the whole OS to stall in a way that you cannot recover from, then by definition there's a bug in the OS. You must ALWAYS be able to kill the offending program and resume normal operation without having to stop one single application other than the offending one. I have no idea whether the bug is actually in Xorg or somewhere else; the reason I'm reporting it against xorg is that ctrl+alt+F1 wouldn't work. I might very well be wrong but I believe xorg is responsible for providing the virtual terminal via ctrl+alt+f1? Either way, that MUST ALWAYS be available no matter how badly things go. That a single program hanging causes me to have to force-power down the computer is outrageous. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Nov 23 17:27:22 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2233 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-169-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
[Desktop-packages] [Bug 1853707] Re: Whole system stopped responding because of single program's fault - no way out, had to force power off
This is not incomplete. Just because the reporter has been asked to provide more information the next time they observe the bug, doesn't mean the report is incomplete. There is enough information for somebody to look at it. Another thing is that nobody wants to or they have better things to do, but a bug shouldn't expire because of that. (actually, bugs shouldn't expire for any reason as long as they understandably describe an issue that exists) ** Summary changed: - Whose system stopped responding because of single program's fault - no way out, had to force power off + Whole system stopped responding because of single program's fault - no way out, had to force power off ** Changed in: compiz (Ubuntu) Status: Expired => New ** Changed in: xorg-server (Ubuntu) Status: Expired => New ** Changed in: unity (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1853707 Title: Whole system stopped responding because of single program's fault - no way out, had to force power off Status in compiz package in Ubuntu: New Status in unity package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: What I did was: - install LibreCAD (by adding their ppa and then using apt-get) - open it - try to open the attached .dwf file LibreCAD hanged and the whole system stopped responding. The mouse button stopped moving, the system wouldn't respond to keyboard strokes, AND not even Ctrl+Alt+F1 worked to open a virtual terminal where I could have tried killing some process. Obviously there's a bug in LibreCAD, but no matter how badly a buggy (or even evil) process behaves, if a single misbehaving program can cause the whole OS to stall in a way that you cannot recover from, then by definition there's a bug in the OS. You must ALWAYS be able to kill the offending program and resume normal operation without having to stop one single application other than the offending one. I have no idea whether the bug is actually in Xorg or somewhere else; the reason I'm reporting it against xorg is that ctrl+alt+F1 wouldn't work. I might very well be wrong but I believe xorg is responsible for providing the virtual terminal via ctrl+alt+f1? Either way, that MUST ALWAYS be available no matter how badly things go. That a single program hanging causes me to have to force-power down the computer is outrageous. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Nov 23 17:27:22 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2233 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-169-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version:
[Desktop-packages] [Bug 1853707] [NEW] Whose system stopped responding because of single program's fault - no way out, had to force power off
Public bug reported: What I did was: - install LibreCAD (by adding their ppa and then using apt-get) - open it - try to open the attached .dwf file LibreCAD hanged and the whole system stopped responding. The mouse button stopped moving, the system wouldn't respond to keyboard strokes, AND not even Ctrl+Alt+F1 worked to open a virtual terminal where I could have tried killing some process. Obviously there's a bug in LibreCAD, but no matter how badly a buggy (or even evil) process behaves, if a single misbehaving program can cause the whole OS to stall in a way that you cannot recover from, then by definition there's a bug in the OS. You must ALWAYS be able to kill the offending program and resume normal operation without having to stop one single application other than the offending one. I have no idea whether the bug is actually in Xorg or somewhere else; the reason I'm reporting it against xorg is that ctrl+alt+F1 wouldn't work. I might very well be wrong but I believe xorg is responsible for providing the virtual terminal via ctrl+alt+f1? Either way, that MUST ALWAYS be available no matter how badly things go. That a single program hanging causes me to have to force-power down the computer is outrageous. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Nov 23 17:27:22 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2233 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-169-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Nov 23 17:25:58 2019 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial ** Attachment added: "wecancut.dwg" https://bugs.launchpad.net/bugs/1853707/+attachment/5307277/+files/wecancut.dwg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed
[Desktop-packages] [Bug 1852763] [NEW] Systematically tries to connect to wifi at startup even though ethernet cable connected
Public bug reported: There's a WiFi network to which I sometime connected and saved it and set it to automatically connect when available; however the password was changed, so whenever my laptop automatically tries to connect to that network, I get the prompt to enter the password. So far all expected. What is unexpected is the following: What I do is: - plug my laptop to the office LAN via an ethernet cable - turn on the laptop Expected: after boot, the computer should connect to the wired network, and hence not attempt to connect to the WiFi network Observed: every single time I boot, 100% systematically, I get the prompt that says that it couldn't connect to the WiFi network and asks me to enter the password manually. The popup shows up even before I log in (usually even before the login screen shows up, when part of the screen is still a mess with random garbage presumably from the uninitialized GPU memory). This most likely means one of two things: either the network manager attempts to connect to the WiFi network before it checks the wired network (by the time I dismiss the prompt the wired network is already connected), or it attempts to connect to WiFi even though it is already connected to the wired network. Either way the behavior is wrong. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194 Uname: Linux 4.4.0-166-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.20 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 15 16:20:10 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (2225 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.37 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-20T16:52:59.722501 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 662a0c09-71a8-4101-9236-ebcc1696d69a /org/freedesktop/NetworkManager/ActiveConnection/1 wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1852763 Title: Systematically tries to connect to wifi at startup even though ethernet cable connected Status in network-manager package in Ubuntu: New Bug description: There's a WiFi network to which I sometime connected and saved it and set it to automatically connect when available; however the password was changed, so whenever my laptop automatically tries to connect to that network, I get the prompt to enter the password. So far all expected. What is unexpected is the following: What I do is: - plug my laptop to the office LAN via an ethernet cable - turn on the laptop Expected: after boot, the computer should connect to the wired network, and hence not attempt to connect to the WiFi network Observed: every single time I boot, 100% systematically, I get the prompt that says that it couldn't connect to the WiFi network and asks me to enter the password manually. The popup shows up even before I log in (usually even before the login screen shows up, when part of the screen is still a mess with random garbage presumably from the uninitialized GPU memory). This most likely means one of two things: either the network manager attempts to connect to the WiFi network before it checks the wired network (by the time I dismiss the prompt the wired network is already
[Desktop-packages] [Bug 1539964] Re: file information not shown on rollover on tab if window is maximized
This is still an issue in 16.04. Why the fuck was this closed?? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1539964 Title: file information not shown on rollover on tab if window is maximized Status in gedit package in Ubuntu: Won't Fix Bug description: Steps to reproduce: 1. open several files in Gedit 2. maximize the window 3. move the cursor over each tab Expected behavior: every time you roll over a tab, a black rectangle should appear with white text with information about the file (full path, mime type...) Observed result: for the left-most tabs and while the cursor x position is lower than a certain point, the info box is not shown. Instead, a strange flickering can be observed on the top left corner of the screen (not even in the area where the info box is supposed to be shown); sometimes you may see the info box appear for a fraction of an instant. If you move the cursor to the right of a certain threshold and for subsequent tabs, it works as expected. Just another pathetic regression in f***ing-unusable 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 30 19:09:37 2016 InstallationDate: Installed on 2013-10-11 (841 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: Upgraded to wily on 2016-01-18 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1539964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
Debate? I haven't seen any debate. And no, your proposed "solution" is no solution to the issue. That's a good possible improvement to the search itself, but type-ahead should do select, NOT search for the obvious reasons that have already been pointed out which are not solved by your proposed improvements to the search -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
Why the f*** has nothing been done on this for over a year? > Could someone having the issue record a screencast showing the bug? Do you need a screencast because you are too lazy to read my description of the issue which is in my original report and perfectly describes what happens, or because you genuinely doubt that I might be making this up? Or is my english really so bad that my description of the issue isn't clear enough? I think you can literally picture it in your head by reading it, but of course I'm biased because I wrote it myself and I've seen the issue. Yet I find it really difficult to believe that anyone familiar with Nautilus, even without having ever observed the issue, would have any difficulty in understanding what I describe. By the way, now I found out that my Trash folder (in home/.local/share/Trash) was about 140 GB. There's obviously something wrong with that. I certainly haven't deleted 100 GB (nor even anywhere near one GB) in the last few months, and I assume the trash is supposed to get emptied automatically from time to time. Now I did "empty Trash" from nautilus and during the whole time it took, it kept flickering just as described in the issue report as it usually happens when deleting folders with "many" files in them. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Confirmed Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831644] [NEW] Automatically connects to wifi though already connected to wired; plus even if previously explicitly disconnected from wifi
Public bug reported: I have a wifi network to which sometimes I connected and stored the password. I am connected to the wired ethernet network. Expected: shouldn't ever connect to any available wifi while I'm connected to wired. Observed: sometimes, randomly, it automatically connects to the wifi despite the fact I'm already connected to wired. As a result, I am then connected to both. Also, it does so at a completely random time: I've been here for hours, the wifi has been available for hours, I've been connected to the wired network all the time, nothing special has happened, I haven't restarted the commputer or logged out and in or anyhthing (I don't know if the wifi has become unavailable for a very short interval of time and then available again, it's unlikely and it wouldn't in any way justify the behavior), yet for some reason, NOW my computer decides to connect to the wifi (which it shouldn't anyway for any reason). ADDITIONALLY: After that, I explicitly manually disconnect from that wifi network. When I do this, I expect that the setting to automatically reconnect to this wifi network when available is turned off (otherwise, every time you disconnect from a network, it would reconnect immediately). I'm pretty sure this used to work. But then, the same as described above happened AGAIN: that is, I was connected to the wired network (had been for hours), and suddenly it automatically connected to the same wifi network as above (again, been available forever), which it shouldn't even if it was set to automatically connect whern available (given it's connected to wired), but it isn't even more nonsensical given that I had previously manually disconnected from it so it should not be set to reconnect automatically. This has started happening recently. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 4 18:35:11 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (2061 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 100 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.37 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-20T16:52:59.722501 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 662a0c09-71a8-4101-9236-ebcc1696d69a /org/freedesktop/NetworkManager/ActiveConnection/2 wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1831644 Title: Automatically connects to wifi though already connected to wired; plus even if previously explicitly disconnected from wifi Status in network-manager package in Ubuntu: New Bug description: I have a wifi network to which sometimes I connected and stored the password. I am connected to the wired ethernet network. Expected: shouldn't ever connect to any available wifi while I'm connected to wired. Observed: sometimes, randomly, it automatically connects to the wifi despite the fact I'm already connected to wired. As a result, I am then connected to both. Also, it does so at a completely random time: I've been here for hours, the wifi has been available for hours, I've been connected to the wired network all the time, nothing special has happened, I haven't restarted the commputer or logged out and in or anyhthing (I don't know if the wifi has become unavailable for a very short interval
[Desktop-packages] [Bug 1828678] [NEW] Nautilus window outside the screen, unreachable, after resuming from hibernation
Public bug reported: I always work with an external display connected to my laptop. The external display is selected as the only display, and the laptop's built-in screen is switched off. Often I hibernate, move the laptop to another place (e.g. from home to the workplace and viceversa), connect a different external screen, and resume from hibernation. When I do so, it often happens that, if I had one or more Nautilus windows open before hibernation, one or more of them are partially or completely outside the screen. When they are partially, they are moved way to the left, and only the right-most part of the window is visible at the left of the screen. In this case I can reach the window with the mouse cursor, click and drag it to the right so it's completely within the screen. But sometimes, the window is completely unreachable, as if it's completely outside the screen (presumably to the left of it, since when it's reachable, it's always to the left). In these cases, there's NOTHING I can do to reach the window and gain access to it. I can right-click on the Launcher icon of the window, but that doesn't give me any way (none that is discoverable, at least) to bring the "lost" window into the visible area of the screen. This sounds mostly like a bug in Xorg or Compiz whatever the window manager is. The fact that it is even POSSIBLE for a window to be moved completely outside of the screen in such a way that you have no way to get access to it, IS certainly a bug or design flaw in whatever piece of software is responsible for managing windows. So is the fact that, when that happens, there is no tool for gaining access to it. However, I have never, ever observed this with windows belonging to any other application except Nautilus. When I hibernate and resume, I usually have several windows open belonging to different applications: Thunderbird, Chrome, Filezilla, Gimp, and others, and often several terminal windows. Yet it has never, ever happened to me that one of them was completely or mostly outside of the screen as it happens with Nautilus. So there seems to be something specific to Nautilus. So it looks like Nautilus is doing something wrong, or failing to do something it's supposed to do, though the fact that the system even allows it to happen, means there's also a bug in the system (whether it's Xorg, Compiz, Unity or whatever). Note that this is a very critical issue, as not being able to access a window means potentially lose work. Fortunately, being a file explorer (as opposed to some other program where you may have unsaved changes to some document), usually the damage is small. However, you may have carefully chosen a set of folders that you have opened in tabs, and/or you may have carefully selected a particular set of files in each tab; having to close the window means you have to repeat the process of selecting those files and folders. That is just an example of loss of work due to this bug. So before wrongly assigning it low importance as you often do, think twice. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 11 16:21:00 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1183x822+670+1147'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2037 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1828678 Title: Nautilus window outside the screen, unreachable, after resuming from hibernation Status in nautilus package in Ubuntu: New Bug description: I always work with an external display connected to my laptop. The external display is selected as the only display, and the laptop's built-in screen is switched off. Often I hibernate, move the laptop to another place (e.g. from home to the workplace and viceversa), connect a different external screen, and resume from hibernation. When I do so, it often happens that, if I had one or more Nautilus windows open before hibernation, one or more of them are partially or completely outside the screen. When they are
[Desktop-packages] [Bug 1827131] Re: Restore type-ahead select (i.e. #1164016)
*** This bug is a duplicate of bug 1754069 *** https://bugs.launchpad.net/bugs/1754069 I forgot I had already filed a new bug report over a year ago. Marked as duplicate. ** This bug has been marked a duplicate of bug 1754069 Restore type-ahead find in Ubuntu 17.10 and later -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1827131 Title: Restore type-ahead select (i.e. #1164016) Status in nautilus package in Ubuntu: Confirmed Bug description: It has long been known that #1164016 has regressed, but for some reason nobody yet has changed back the status of the bug from "fix released", so (since I can't do that) I'm opening a new one. Feel free to mark this as duplicate if (and only if) #1164016 is reopened. All the information is there. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 30 22:19:55 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1135x824+526+137'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2027 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1827131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
> The Gnome team is extremely resistant to bring back the old intuitive > functionality. > I tried to explain the problems at > https://gitlab.gnome.org/GNOME/nautilus/issues/244 > , as did many others. Trying to reason with the Gnome team is a complete waste of time. That's why Ubuntu should either patch it, or drop Nautilus completely. Why the f*** is this bug still in the "fix released" status? It should either be reopened or a new one created. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827131] [NEW] Restore type-ahead select (i.e. #1164016)
Public bug reported: It has long been known that #1164016 has regressed, but for some reason nobody yet has changed back the status of the bug from "fix released", so (since I can't do that) I'm opening a new one. Feel free to mark this as duplicate if (and only if) #1164016 is reopened. All the information is there. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 30 22:19:55 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1135x824+526+137'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2027 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug third-party-packages xenial ** Changed in: nautilus (Ubuntu) Status: New => Incomplete ** Changed in: nautilus (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1827131 Title: Restore type-ahead select (i.e. #1164016) Status in nautilus package in Ubuntu: Confirmed Bug description: It has long been known that #1164016 has regressed, but for some reason nobody yet has changed back the status of the bug from "fix released", so (since I can't do that) I'm opening a new one. Feel free to mark this as duplicate if (and only if) #1164016 is reopened. All the information is there. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 30 22:19:55 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1135x824+526+137'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2027 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1827131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
How is this importance low??? The Nautilus UI remains unusable while this happens, which may take several seconds. Also, when a user sees this happen after deleting some files (which clearly means Nautilus is "doing something" related to deleting the files), one can't be sure whether it's safe to go on doing other stuff (e.g. copying folders or uploading them somewhere) before the flickering ends, i.e. before nautilus is done doing whatever it's doing. I always wait just in case. Which again may be several seconds. This is a huge usability issue. ** Changed in: nautilus (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Confirmed Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
> This is a huge usability issue. and until we know exactly what is going on when the flickering happens, we don't know for sure whether it's more than a mere usability issue. So until that's known for sure, this should have importance high or critical. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Confirmed Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
> In reality, > recursive search is useful, and I want to use it, but it's different to > typeahead Exactly, they are two completely different, unrelated things, and if the Nautilus devs can't understand something as elementary as that, Ubuntu shouldn't be using software developed by those people as the default file explorer. This issue is just one example; nautilus developers have taken quite a few "design decisions" that are - ahem - let's say contrary to common sense, degrading usability rather than improve things. Keeping Nautilus as the file explorer means Ubuntu will have to keep struggling with this sort of things and maintaining patches like this one. Of course, if there's no better alternative out there (I find it hard to believe that such a shitty file manager is the best available, but I don't know, it might be), then it'll have to be this. > I do think things will eventually go back this way > (...) I do think Nautilus can satisfy everyone's preferences here How long do we have to wait for them to recapacitate and revert breaking stuff that had been designed correctly in the first place ages ago? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792722] Re: Restarting unity-settings-daemon screws up Nautilus settings, needs Nautilus restart
Is the fix available for 16.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792722 Title: Restarting unity-settings-daemon screws up Nautilus settings, needs Nautilus restart Status in nautilus package in Ubuntu: Fix Released Bug description: UPDATE: see comment 2 From time to time, these two bugs resurface, which were fixed ages ago: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1130722 https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1731985 and also: the font type and/or size in Nautilus changes to a smaller and less readable font. The three things always reappear at once. Then everything goes back to expected; I'm not sure if that's when I get some new updates installed or when I just reboot. It seems to me that all these issues are things that got changed upstream in Nautilus, but patched in Ubuntu because Ubuntu maintainers have some more common sense than the Nautilus developers. I don't know if (a) sometimes someone forgets to apply some patches, and an unpatched version slips into Ubuntu's packages until somebody corrects it, or (b) some configuration gets randomly lost/changed and then restored/changed back on reboot. Either way, it's f***ing annoying. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 15 18:25:09 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1799 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
There's no need for an option. You can already do a recursive search with Ctrl+F. I "can't believe" one would want to enable type-ahead-recursive-search instead of type-ahead-select-in-current-folder by default just to spare themselves the trouble of hitting Ctrl+F. However, an option, even if for enabling the weirdest preference or for accomodating the rarest use case, is always a good thing. What is absolutely unacceptable is a wrong default behavior that, even worse, cannot even be changed to the more sensible one. That is, the current situation. I am stuck with 16.04 because upgrading to 18.04 would mean having to live with this crap, which is like living without a file explorer at all (that's doable for somebody accustomed to doing everyday tasks from a terminal, but that's not me, nor the average user). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
Yeah right. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
@Javier if by "they" you mean the upstream Nautilus developers, that's right: they don't even understand it's a bug. The Gnome development team, or at least the part responsible for Naitulus, has proven many times to be a bunch of idiots. For the last several years, they have taken many design decision that completely destroyed the usability of their software. But the Ubuntu team seems to be more intelligent. In the past they have patched several things in Nautilus and perhaps other Gnome products to fix the idiotic mistakes made upstream. This was one of them. Now the question is: does Ubuntu consider it worth to keep doing the patching to fix the upstream idiocies in Nautilus? If that is the case, then this, among other things, needs to be fixed. Again. If not, if they are going to rely on the upstream developers fixing upstream issues, then they must drop Nautilus in favor of some other file manager that is not maintained by a bunch of idiots. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759714] Re: [nvidia] Xorg suddenly starts to consume 100% CPU, apparently triggered by Chrome
> Please follow the steps in comment #2 if you would like any help. > If you don't have time then no problem, just let the bug expire. The very idea of bugs expiring because the OP doesn't provide any given piece of information is stupid. I'm always puzzled at how it's such a common practice in bug trackers. It makes no sense to close a bug unless it's either fixed or found to be invalid. What's the point in waiting for other people to stumble on the same bug and report it again and again? Also you're demanding an unreasonable amount of work on the side of the reporter (yes, I know, you're not "demanding" anything strictly speaking, but I mean expecting it to be done by the reporter rather than by the developers or triagers): to uninstall a driver and test whether the bug is still present in a completely different configuration. Whatever the answer is, the bug exists and isn't any less of a bug: the test would serve the purpose of TRIAGING the bug, which is not something that can reasonably be expected to be done by the user. Now, of course it never hurts to ask the reporter to try something, but putting the bug in "incomplete" status (which implies it expiring if the original poster doesn't do that) is wrong. That's like closing a bug because it's too difficult to fix (note that difficult to reproduce just mean difficult to investigate which in turn means difficult to fix: that does not make it any less of an issue or mean it's any less severe; if anything it means it needs more attention, not less). Actually that's exactly what it is, and it is done a lot, which is what frustrates me (and part of the reason why Ubuntu is so buggy). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1759714 Title: [nvidia] Xorg suddenly starts to consume 100% CPU, apparently triggered by Chrome Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I navigated to a website in Chrome (linledIn.com) and both Chrome and Xorg started consuming around 100% CPU each (one was actually significantly above 100% but I can't remember which one). Then I closed Chrome entirely (and I check there was no Chrome process left), but Xorg kept consuming around 100% CPU. No other process was. I closed all applications I had opened, but nothing stopped Xorg from consuming around 100% CPU while nobody was doing nothing. I had to kill Xorg. It might have been a complete coincidence that Xorg's crazy CPU usage started when I opened that website in Chrome, or it might actually have been caused by it, even by a bug in Chrome. But even if that is the case, if an application can cause Xorg to consume 100% CPU and then not stop even after the application has been closed, that is a bug in Xorg. Also, something quite similar happens to me very often: sometimes I open Google Maps in Chrome and (not every time, far from it), the same as described above happens, that is, both Chrome and Xorg start consuming a lot of CPU. However, in those cases, usually when I close Chrome, Xorg's CPU consumptions goes back to normal (and then I'm able to reopen Chrome and everything works normally). This was the first time that Xorg's abnormal CPU consumption persisted after closing Chrome which seemed to have triggered it. I'm not sure whether the two cases are actually caused by the same issue or not. I know I'm providing little information but this is all I have. Note that the issue is critical. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Mar 29 00:50:20 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
Why the fuck hasn't this been reopened yet?? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
> Do you still see that problem in newer Ubuntu versions? I see it in 16.04 (as in the report) which is LTS and still supposed to be supported. I haven't tested any later version. I can't upgrade to 18.04 because of #1164016 which renders Nautilus completely unusable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Incomplete Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1277180] Re: dotted rectangles remain drawn in window after copying a bunch of files
I do think I have seen it recently, but can't tell for sure. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1277180 Title: dotted rectangles remain drawn in window after copying a bunch of files Status in nautilus package in Ubuntu: Incomplete Bug description: I copyed a bunch of files from a Nautilus window into another by Ctrl+dragging and dropping them. Both windows were set with icons visualization, so when I (ctrl)dragged and dropped the icons, dotted rectangles were drawn and dragged, as expected. However, after dropping the files, which were succesfully copied, the dotted rectangles should have disappeared, but they remained, as if printed on the destination window. Neither by moving, nor by minimizing and remaximizing the window, could I get rid of the spurious dotted rectangles. Even while navigating to other folders, the dotted rectangles stay there. Even after resizing the window. Despite the contents of the window being redrawn and updated, the dotted rectangles are still there, and they move around while I move around the window, as if they were part of its contents. The only way to have them disappear is to completely close the window. Obviously this is not systematically reproducible. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Thu Feb 6 18:15:28 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1059x698+434+254'" InstallationDate: Installed on 2013-10-11 (117 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1277180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1277180] Re: dotted rectangles remain drawn in window after copying a bunch of files
I'm not sure, since it's always been random and never systematically reproducible. I'm using 16.04 now (can't upgrade to 18.04 mostly because of #1164016), if I observe it again I'll try to remember to comment here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1277180 Title: dotted rectangles remain drawn in window after copying a bunch of files Status in nautilus package in Ubuntu: Incomplete Bug description: I copyed a bunch of files from a Nautilus window into another by Ctrl+dragging and dropping them. Both windows were set with icons visualization, so when I (ctrl)dragged and dropped the icons, dotted rectangles were drawn and dragged, as expected. However, after dropping the files, which were succesfully copied, the dotted rectangles should have disappeared, but they remained, as if printed on the destination window. Neither by moving, nor by minimizing and remaximizing the window, could I get rid of the spurious dotted rectangles. Even while navigating to other folders, the dotted rectangles stay there. Even after resizing the window. Despite the contents of the window being redrawn and updated, the dotted rectangles are still there, and they move around while I move around the window, as if they were part of its contents. The only way to have them disappear is to completely close the window. Obviously this is not systematically reproducible. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Thu Feb 6 18:15:28 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1059x698+434+254'" InstallationDate: Installed on 2013-10-11 (117 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1277180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759714] Re: [nvidia] Xorg suddenly starts to consume 100% CPU, apparently triggered by Chrome
Just because using Nvidia is "optional" and I don't have time to waste trying uninstalling it, doesn't mean this bug should expire. By the way, when you say "using Nvidia on this laptop is optional" do you mean actually using the Nvidia GPU is (no shit!) or that I can uninstall the nvidia drivers and still be using the NVidia GPU fully?? ** Changed in: xorg-server (Ubuntu) Status: Expired => Confirmed ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1759714 Title: [nvidia] Xorg suddenly starts to consume 100% CPU, apparently triggered by Chrome Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: I navigated to a website in Chrome (linledIn.com) and both Chrome and Xorg started consuming around 100% CPU each (one was actually significantly above 100% but I can't remember which one). Then I closed Chrome entirely (and I check there was no Chrome process left), but Xorg kept consuming around 100% CPU. No other process was. I closed all applications I had opened, but nothing stopped Xorg from consuming around 100% CPU while nobody was doing nothing. I had to kill Xorg. It might have been a complete coincidence that Xorg's crazy CPU usage started when I opened that website in Chrome, or it might actually have been caused by it, even by a bug in Chrome. But even if that is the case, if an application can cause Xorg to consume 100% CPU and then not stop even after the application has been closed, that is a bug in Xorg. Also, something quite similar happens to me very often: sometimes I open Google Maps in Chrome and (not every time, far from it), the same as described above happens, that is, both Chrome and Xorg start consuming a lot of CPU. However, in those cases, usually when I close Chrome, Xorg's CPU consumptions goes back to normal (and then I'm able to reopen Chrome and everything works normally). This was the first time that Xorg's abnormal CPU consumption persisted after closing Chrome which seemed to have triggered it. I'm not sure whether the two cases are actually caused by the same issue or not. I know I'm providing little information but this is all I have. Note that the issue is critical. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Mar 29 00:50:20 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (1629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz
[Desktop-packages] [Bug 1650341] Re: [16.04 REGRESSION] gedit listed twice in context menu "open with"
How do I get the fix on 16.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1650341 Title: [16.04 REGRESSION] gedit listed twice in context menu "open with" Status in nautilus package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. In Nautilus, navigate to a folder containing some XML file 2. Right-click on a .xml file 3. Click or hover on "open with" Expected: in the list of applications in the submenu, Gedit should be listed once and only once Observed: it is listed twice. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Dec 15 18:29:09 2016 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1814x957+191+329'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1160 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to xenial on 2016-12-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1650341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1577005] Re: Syntax highlight randomly stops being updated
Thank you for looking at the bug for the first time 2 years and a half after it was reported. The issue is still present at least on 16.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1577005 Title: Syntax highlight randomly stops being updated Status in gedit package in Ubuntu: Won't Fix Bug description: At random times it happens, while editing a text file in some programming language (I see it daily with PHP files), that: - you are editing the file somewhere in the middle of it - you type some unmatched opening quote, for example you start typing a string assignment. At this point all the syntax from where you are through the end of the file is screwed up, as expected (mostly "pink", or whatever the color of strings is) - then when you do type the matching closing quote sign that was missing, and the syntax is now correct, a huge portion of the file still doesn't get refreshed, that is, it remains with the wrong screwed-up syntax highlight. By moving the cursor somewhere in the part of the code whose syntax highlight hasn't been updated, usually the whole file gets properly syntax-highlighted again. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 30 18:03:41 2016 InstallationDate: Installed on 2013-10-11 (931 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: Upgraded to wily on 2016-01-18 (103 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1577005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1535461] Re: [15.10 REGRESSION] Find has become sensitive to differences in accents
The issue is still present on 16.04. It would have taken less for you to try and see that than it probably took to post comment #2 and close the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1535461 Title: [15.10 REGRESSION] Find has become sensitive to differences in accents Status in gedit package in Ubuntu: Won't Fix Bug description: Steps to reproduce: - write (or paste, or load) a text containing the string "maría" - hit Ctrl+F - in the search box, type "maria" Expected: should find the string "maría" in the text, because í and i only differ by an accent. This is the way it used to work, and it is the way every decent editor works Observed: doesn't find the matching string unless you type it exactly with the same accents. I already reported this upstream at https://bugzilla.gnome.org/show_bug.cgi?id=760810 However, they'll probably tell me that I'm using a too old version. - Please check whether it is already fixed in a later version upstream - if so, release the fixed version in Ubuntu - if not, either patch it or immediately roll back to the version without the issue. This makes ctrl+F unusable. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 18 22:54:37 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1535461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1535461] Re: [15.10 REGRESSION] Find has become sensitive to differences in accents
> please add a comment here telling us which new version it is in and change the bug status to Confirmed You should update the text of that comment and remove the part that says to change the status to confirmed, because the system doesn't allow me to do that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1535461 Title: [15.10 REGRESSION] Find has become sensitive to differences in accents Status in gedit package in Ubuntu: Won't Fix Bug description: Steps to reproduce: - write (or paste, or load) a text containing the string "maría" - hit Ctrl+F - in the search box, type "maria" Expected: should find the string "maría" in the text, because í and i only differ by an accent. This is the way it used to work, and it is the way every decent editor works Observed: doesn't find the matching string unless you type it exactly with the same accents. I already reported this upstream at https://bugzilla.gnome.org/show_bug.cgi?id=760810 However, they'll probably tell me that I'm using a too old version. - Please check whether it is already fixed in a later version upstream - if so, release the fixed version in Ubuntu - if not, either patch it or immediately roll back to the version without the issue. This makes ctrl+F unusable. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 18 22:54:37 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1535461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1188569] Re: Some keyboard shortcuts randomly stop working
@18 Does that explain that the issue happens RANDOMLY - i.e. every time I boot, shortcuts may or may not be working? In my case all of these shortcuts stop working at once (i.e. either they all work, or none of them does, never some and some): - Ctrl+Alt+T - all or most special keys, e.g. Volume +/-/mute, switch screens (which on my laptop is Fn+F6) - PrintScreen and Shift+PrintScreen - maybe others that I don't remember. Killing unity-settings-daemon (which automatically restart) systematically fixes it. But it breaks stupid Nautilus, so then I have to kill and relaunch Nautilus too. Is this actually the same issue?? And if so, what's the fix for 16.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1188569 Title: Some keyboard shortcuts randomly stop working Status in GNOME Shell: New Status in Unity: Confirmed Status in unity package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: Hi, Certain shortcuts randomly stops working in my computer. They are Super+s (workspace switcher), Super+Up (switch to workspace above) and Super+Down (switch to workspace below). Other shortcuts work fine. A few notes that might help: 1- Reassigning shortcuts make them work again except for Super+s. 2- Rebooting make shortcuts work. 3- I have been using these shortcuts with many previous ubuntu versions and my preferences are old. 4- I am not sure of certain steps that produces the problem. The shortcuts sometimes stop working but once they stop, they do not work unless I reassign them or reboot. I am using Ubuntu 13.04. Thank you ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,grid,mousepoll,place,wall,snap,resize,vpswitch,session,animation,gnomecompat,imgpng,commands,move,workarounds,fade,unitymtgrabhandles,expo,scale,ezoom,unityshell] Date: Fri Jun 7 13:40:06 2013 InstallationDate: Installed on 2013-05-27 (11 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1188569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759282] Re: randomly become unable to open new Nautilus windows
Still observing the issue. Please change the value of importance to a sensible one, this is medium/high. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1759282 Title: randomly become unable to open new Nautilus windows Status in nautilus package in Ubuntu: Confirmed Bug description: At random times after having the system running for a few hours this starts happening: - I don't have any Nautilus window open (I previously dad and at some point closed all of them) - I click on Nautilus' launcher icon - it kind of blinks for like 30 seconds (by the way, that's barely noticeable, that sucks on its own) and then nothing happens, no Nautilus window opens up, no error message shows up (that's another thing that is wrong on its own, you should ALWAYS get an error message when something fails) and the Launcher icon finally stops blinking. I retry a few times, same result. So I open a terminal and try to launch Nautilus from there, so at least I get the fucking error messages: $ nautilus (nautilus:18764): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed (nautilus:18764): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Could not register the application: Timeout was reached (nautilus:18764): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed (nautilus:18764): GLib-GObject-WARNING **: invalid (NULL) pointer instance (nautilus:18764): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed For fuck's sake please switch to some other file manager, Nautilus is pathetic. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 27 16:03:32 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1197x691+309+248'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1627 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1759282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794139] [NEW] At random times, no warning when closing a file after it's been deleted
Public bug reported: See https://gitlab.gnome.org/GNOME/gedit/issues/73#note_331812 Closed upstream because gedit version too old. It seem I never get it right. When I report an issue here I get told to report it upstream, and viceversa. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 24 17:46:45 2018 InstallationDate: Installed on 2013-10-11 (1808 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1794139 Title: At random times, no warning when closing a file after it's been deleted Status in gedit package in Ubuntu: New Bug description: See https://gitlab.gnome.org/GNOME/gedit/issues/73#note_331812 Closed upstream because gedit version too old. It seem I never get it right. When I report an issue here I get told to report it upstream, and viceversa. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 24 17:46:45 2018 InstallationDate: Installed on 2013-10-11 (1808 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1794139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731985] Re: Nautilus now makes random beeps on some navigation actions, and I can't turn it off
Mistery solved: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792722/comments/2 ** Changed in: nautilus (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1731985 Title: Nautilus now makes random beeps on some navigation actions, and I can't turn it off Status in nautilus package in Ubuntu: Invalid Bug description: Since a recent update, Nautilus has begun to make sounds as I navigate folders. (1) There is NO WAY AT ALL to turn these sounds off, without turning off also other unrelated and useful sounds, see https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1731982 Besides: (2) Navigating through folders in a file explorer is something too common to have sounds on by default. It's annoying. They should be DISABLED BY DEFAULT, period. I understand there might be a handful of people in the world who may like them (not these ones in particular, of course), but the default should be Off. (3) These sounds are CRAP. They don't sound like anything that you may find in other OSes for this kind of scenario, they are too loud and bold, and they are nothing that remotely conveys the action that is being performed. Something reasonable would be a "click" sound, which would also be less annoying (4) The behavior is inconsistent and stupid: When you double click on a folder within the window to open it, it doesn't make any sound. But when you click on an item in the "breadcrumbs" on the top of the window, then it does make a sound. That makes no sense. Either you play sounds at all navigating actions, or none. I reported this upstream, but this has been their answer: https://gitlab.gnome.org/GNOME/nautilus/issues/118 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 13 18:34:38 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1277x824+493+148'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1494 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1731985/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792722] Re: Ubuntu patches to nautilus get randomly reverted again and again
I found out what triggers this issue! This happens when I restart (by killing it) unity-settings-daemon as a workaround to infamous bug 1731294. And now I see that there is a workaround to the workaround. After killing unity-settings-daemon (which restarts automatically), which leaves Nautilus all screwed up with its crappy font, its stupid random beep sounds, and its unusable mess of menus, I have to kill every last running instance of Nautilus (it's not enough to close all nautilus window, you need to kill the one responsible for the Desktop), and restart it. Then it works as expected. Note that, even though this surfaces as a consequence of a workaround to issue 1731294, this is an issue on its own: restarting unity-settings-daemon shouldn't leave a running instance of Nautilus in a crippled state. Either Nautilus should restart automatically if necessary, or it shouldn't be affected in the first place. I don't know whether this is unity-settings-daemon's fault or Nautilus' fault, but it's certainly not expected behavior. ** Summary changed: - Ubuntu patches to nautilus get randomly reverted again and again + Restarting unity-settings-daemon screws up Nautilus settings, needs Nautilus restart ** Description changed: + UPDATE: see comment 2 + From time to time, these two bugs resurface, which were fixed ages ago: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1130722 https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1731985 and also: the font type and/or size in Nautilus changes to a smaller and less readable font. - The three things always reappear at once. Then everything goes back to expected; I'm not sure if that's when I get some new updates installed or when I just reboot. It seems to me that all these issues are things that got changed upstream in Nautilus, but patched in Ubuntu because Ubuntu maintainers have some more common sense than the Nautilus developers. - I don't know if + I don't know if (a) sometimes someone forgets to apply some patches, and an unpatched version slips into Ubuntu's packages until somebody corrects it, or (b) some configuration gets randomly lost/changed and then restored/changed back on reboot. Either way, it's f***ing annoying. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 15 18:25:09 2018 GsettingsChanges: - b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' - b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" - b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' - b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" + b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' + b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" + b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' + b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1799 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792722 Title: Restarting unity-settings-daemon screws up Nautilus settings, needs Nautilus restart Status in nautilus package in Ubuntu: New Bug description: UPDATE: see comment 2 From time to time, these two bugs resurface, which were fixed ages ago: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1130722 https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1731985 and also: the font type and/or size in Nautilus changes to a smaller and less readable font. The three things always reappear at once. Then everything goes back to expected; I'm not sure if that's when I get some new updates installed or when I just reboot. It seems to me that all these issues are things that got changed upstream in Nautilus, but patched in Ubuntu because Ubuntu maintainers have some more common sense than the Nautilus developers. I don't know if (a) sometimes someone forgets to apply some patches, and an unpatched version slips into Ubuntu's packages until somebody corrects it, or (b) some configuration gets randomly lost/changed and then restored/changed back on reboot. Either way, it's f***ing annoying. ProblemType: Bug
[Desktop-packages] [Bug 1792722] [NEW] Ubuntu patches to nautilus get randomly reverted again and again
Public bug reported: >From time to time, these two bugs resurface, which were fixed ages ago: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1130722 https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1731985 and also: the font type and/or size in Nautilus changes to a smaller and less readable font. The three things always reappear at once. Then everything goes back to expected; I'm not sure if that's when I get some new updates installed or when I just reboot. It seems to me that all these issues are things that got changed upstream in Nautilus, but patched in Ubuntu because Ubuntu maintainers have some more common sense than the Nautilus developers. I don't know if (a) sometimes someone forgets to apply some patches, and an unpatched version slips into Ubuntu's packages until somebody corrects it, or (b) some configuration gets randomly lost/changed and then restored/changed back on reboot. Either way, it's f***ing annoying. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 15 18:25:09 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1799 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792722 Title: Ubuntu patches to nautilus get randomly reverted again and again Status in nautilus package in Ubuntu: New Bug description: From time to time, these two bugs resurface, which were fixed ages ago: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1130722 https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1731985 and also: the font type and/or size in Nautilus changes to a smaller and less readable font. The three things always reappear at once. Then everything goes back to expected; I'm not sure if that's when I get some new updates installed or when I just reboot. It seems to me that all these issues are things that got changed upstream in Nautilus, but patched in Ubuntu because Ubuntu maintainers have some more common sense than the Nautilus developers. I don't know if (a) sometimes someone forgets to apply some patches, and an unpatched version slips into Ubuntu's packages until somebody corrects it, or (b) some configuration gets randomly lost/changed and then restored/changed back on reboot. Either way, it's f***ing annoying. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 15 18:25:09 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1799 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754069] Re: bug 1164016 has regressed
Either reopen #1164016 or keep this one open (since in 1164016 you asked me to open a new one instead). Given that 1164016 was considered valid, and fixed, the arguments given in comment 2 are bullshit. This just needs to be patched again as it was before. And fucking quickly. This infamous regression is making Ubuntu completely unusable (again). I, like probably million other users, am refraining from upgrading just because of this. And those who didn't know and did upgrade are regretting it, as many comments in #1164016 demonstrate. ** Changed in: nautilus (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1754069 Title: bug 1164016 has regressed Status in nautilus package in Ubuntu: Confirmed Bug description: I'm opening this because I can't change back the status of issue 1164016 back from "fix released" (which is so stupid by the way: IF I can change the status from any other status, why shouldn't I be able to change it from "fix released"? Nonsense) https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1164016 Many users have reported the bug is back on 17.10. I can't think of any reason why it should take more than a few minutes to fix it back for 17.10, other than maybe nobody among the people who were responsible for the fix have noticed yet. Feel free to mark this as duplicate *after* you reopen #1164016 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 7 16:29:37 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1254x928+65+124'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1607 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792424] [NEW] Left panel flickers like crazy during several seconds after deleting a bunch of files
Public bug reported: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial ** Attachment added: "Untitled.png" https://bugs.launchpad.net/bugs/1792424/+attachment/5188525/+files/Untitled.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: New Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1791337] Re: Terminal should prompt for confirmation before pasting text containing newlines
> gnome-terminal could warn you before pasting a newline. It could offer > to disable that warning, Yep, it should do both things (I forgot to mention the second one), or, as I said, just require a single Enter keystroke (and still, obviously have a setting to disable that). I don't think having to hit Enter when you paste several lines, just like you usually do when you paste a single line (usually not including the final newline) would be a great annoyance for those who often paste whole sequences of commands, but if it was for someone, there would always be the setting to disable it. > I believe the proper solution is to enable bracketed paste mode Does that address the case where I actually do want to paste a sequence of commands and run them? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1791337 Title: Terminal should prompt for confirmation before pasting text containing newlines Status in gnome-terminal package in Ubuntu: New Bug description: Steps to reproduce: - copy some texts that includes newline characters - paste it (usually accidentally) in a terminal Expected behavior: Before pasting something that will be executed (because newline characters will be processed as if hitting the Enter key), the terminal should prompt for confirmation. OR at least, what you paste should be only displayed and not actually processed until you press the Enter key. THIS SHOULD BE F***ING OBVIOUS, I can't believe I have to report this. Observed behavior: blindly pastes everything and executes each line as a command. THIS IS F***ING DANGEROUS. It's too easy to forget to copy what you actually meant to copy, or forget you copied something else afterwards, and accidentally paste a random block of text of several lines which usually isn't even shell commands, but some of them can actually happen to be valid commands that actually do stuff. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 7 18:32:28 2018 InstallationDate: Installed on 2013-10-11 (1791 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1791337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791337] Re: Terminal should prompt for confirmation before pasting text containing newlines
Obviously this should be fixed upstream, but until then, a decent distribution would patch it to fix such an idiotic behaviour. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1791337 Title: Terminal should prompt for confirmation before pasting text containing newlines Status in gnome-terminal package in Ubuntu: New Bug description: Steps to reproduce: - copy some texts that includes newline characters - paste it (usually accidentally) in a terminal Expected behavior: Before pasting something that will be executed (because newline characters will be processed as if hitting the Enter key), the terminal should prompt for confirmation. OR at least, what you paste should be only displayed and not actually processed until you press the Enter key. THIS SHOULD BE F***ING OBVIOUS, I can't believe I have to report this. Observed behavior: blindly pastes everything and executes each line as a command. THIS IS F***ING DANGEROUS. It's too easy to forget to copy what you actually meant to copy, or forget you copied something else afterwards, and accidentally paste a random block of text of several lines which usually isn't even shell commands, but some of them can actually happen to be valid commands that actually do stuff. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 7 18:32:28 2018 InstallationDate: Installed on 2013-10-11 (1791 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1791337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791337] [NEW] Terminal should prompt for confirmation before pasting text containing newlines
Public bug reported: Steps to reproduce: - copy some texts that includes newline characters - paste it (usually accidentally) in a terminal Expected behavior: Before pasting something that will be executed (because newline characters will be processed as if hitting the Enter key), the terminal should prompt for confirmation. OR at least, what you paste should be only displayed and not actually processed until you press the Enter key. THIS SHOULD BE F***ING OBVIOUS, I can't believe I have to report this. Observed behavior: blindly pastes everything and executes each line as a command. THIS IS F***ING DANGEROUS. It's too easy to forget to copy what you actually meant to copy, or forget you copied something else afterwards, and accidentally paste a random block of text of several lines which usually isn't even shell commands, but some of them can actually happen to be valid commands that actually do stuff. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 7 18:32:28 2018 InstallationDate: Installed on 2013-10-11 (1791 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1791337 Title: Terminal should prompt for confirmation before pasting text containing newlines Status in gnome-terminal package in Ubuntu: New Bug description: Steps to reproduce: - copy some texts that includes newline characters - paste it (usually accidentally) in a terminal Expected behavior: Before pasting something that will be executed (because newline characters will be processed as if hitting the Enter key), the terminal should prompt for confirmation. OR at least, what you paste should be only displayed and not actually processed until you press the Enter key. THIS SHOULD BE F***ING OBVIOUS, I can't believe I have to report this. Observed behavior: blindly pastes everything and executes each line as a command. THIS IS F***ING DANGEROUS. It's too easy to forget to copy what you actually meant to copy, or forget you copied something else afterwards, and accidentally paste a random block of text of several lines which usually isn't even shell commands, but some of them can actually happen to be valid commands that actually do stuff. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-terminal 3.18.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 7 18:32:28 2018 InstallationDate: Installed on 2013-10-11 (1791 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1791337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1130722] Re: [ffe] Restore a traditional menu under Unity
On ubuntu 16.04, after some recent software update (NO dist upgrade) this has regressed again together with a bunch of other crap that was fixed ages ago. Please reopen, and for fuck's sake can you be more careful and avoid fixed bugs reappearing periodically?? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1130722 Title: [ffe] Restore a traditional menu under Unity Status in Ayatana Design: Fix Committed Status in nautilus package in Ubuntu: Fix Released Bug description: When fixing this bug, also take a look at bug #1131664 at the same time if possible. In Nautilus 3.6, introduced in raring, the menu layout was changed from the traditional all-entries-in-one-menubar to: * an application menu called "Files" in the Unity menu bar * a view menu has moved to some toolbar buttons and a dropdown under an arrow in the upper right of a window * all other menu items have moved to a cog button dropdown in the upper right of a window For Unity, we should probably switch back to the more traditional layout (and keep the new layout for GNOME). I'll assign an Ayatana task to get design guidance on what the layout should be. Desired resolution: - Remove the 'cog' icon from the top right of the Nautilus toolbar. Move the view and search buttons over to the right, so that the right most view button occupies the position which previously held the cog button. - Patch Nautilus to have the following menu layout: === File === New Window New Tab - Connect to Server Enter Location - Create New Folder Create New Document> - Properties Restore Missing Files... Ubuntu One - Quit === Edit=== Undo Redo - Select All Select Items Matching... Invert Selection - Cut Copy Paste - Preferences === View === Zoom In Zoom Out Normal Size - Reload - Icons List By Name By Size By Type By Modification Date - Reversed Order - Show Sidebar Show Location Bar text / Hide Location Bar text - Reset View to Defaults Show Hidden Files === Go === Open Parent Back Forward - Location... Search for Files... === Bookmarks === Add Bookmark Edit Bookmark - Home Computer Trash Network [list of all current Nautilus bookmarks] === Help === Help About Files To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1130722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1731985] Re: Nautilus now makes random beeps on some navigation actions, and I can't turn it off
The issue went away misteriously, and now it has come back again. Apparently it reoccurs every few years with software updates. I am reopening the bug report, as it was wrongly closed (see comments 6, 7). ** Changed in: nautilus (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1731985 Title: Nautilus now makes random beeps on some navigation actions, and I can't turn it off Status in nautilus package in Ubuntu: Confirmed Bug description: Since a recent update, Nautilus has begun to make sounds as I navigate folders. (1) There is NO WAY AT ALL to turn these sounds off, without turning off also other unrelated and useful sounds, see https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1731982 Besides: (2) Navigating through folders in a file explorer is something too common to have sounds on by default. It's annoying. They should be DISABLED BY DEFAULT, period. I understand there might be a handful of people in the world who may like them (not these ones in particular, of course), but the default should be Off. (3) These sounds are CRAP. They don't sound like anything that you may find in other OSes for this kind of scenario, they are too loud and bold, and they are nothing that remotely conveys the action that is being performed. Something reasonable would be a "click" sound, which would also be less annoying (4) The behavior is inconsistent and stupid: When you double click on a folder within the window to open it, it doesn't make any sound. But when you click on an item in the "breadcrumbs" on the top of the window, then it does make a sound. That makes no sense. Either you play sounds at all navigating actions, or none. I reported this upstream, but this has been their answer: https://gitlab.gnome.org/GNOME/nautilus/issues/118 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 13 18:34:38 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1277x824+493+148'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1494 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1731985/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
> I can't completely understand what GNOME developers are trying to achieve! > 18.04 LTS and 18.10 are trying to perform search after entering first letter. The underlying assumption seems to be that when you type the name of a file, the only thing you may possibly want is to search for that file, and that if the search is recursive within subdirectory, that's even better, and that the only reason you may not want that, is because a recursive search can become slow; but since they have optimized search so much that it is always instant-fast (or so they claim), then who wouldn't want Nautilus to just start searching recursively and instantly showing you the search results as you type? Genius, right? Wrong. Becaue even assuming a recursive search in a bazillion files could be performed in a nanosecond, that is not necessarily what we want when we type a partial filename. Many of us just want to SELECT a file within the current directory while still viewing all of its contents and not just the matching file/s. Perhaps you want to simply SPOT that file and select other ones that are near to it, or actually select that one but also other ones. When you want to do a search, which is a completely different thing, you can do Ctrl+F. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1786357] [NEW] Indicator tells me I'm connected, but doesn't tell me to which network
Public bug reported: See the screenshot. I am connected to a wifi network, and I have been for a while. The icon shows I'm connected, which is consistent with the fact that I can navigate in Chrome. However, when I click on the wifi icon, the dropdown shows up as shown in the screenshot: under "WiFi networks", just before "Disconnect" (which is another proof that it knows I'm connected) there should be the name of the network I'm connected to. This was like this for several seconds, about a minute, even after closing and reopening the dropdown. Then after a while it fixed itself. There are no conceivable circumstances under which that makes sense, even for a short period of time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-gnome 1.2.6-0ubuntu0.16.04.4 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 10 01:18:22 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (1763 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.43.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.78 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/0 teo moto9a866870-e3e4-4d05-ac38-859782244d07 /org/freedesktop/NetworkManager/ActiveConnection/5 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial ** Attachment added: "Untitled.png" https://bugs.launchpad.net/bugs/1786357/+attachment/5173526/+files/Untitled.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1786357 Title: Indicator tells me I'm connected, but doesn't tell me to which network Status in network-manager-applet package in Ubuntu: New Bug description: See the screenshot. I am connected to a wifi network, and I have been for a while. The icon shows I'm connected, which is consistent with the fact that I can navigate in Chrome. However, when I click on the wifi icon, the dropdown shows up as shown in the screenshot: under "WiFi networks", just before "Disconnect" (which is another proof that it knows I'm connected) there should be the name of the network I'm connected to. This was like this for several seconds, about a minute, even after closing and reopening the dropdown. Then after a while it fixed itself. There are no conceivable circumstances under which that makes sense, even for a short period of time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-gnome 1.2.6-0ubuntu0.16.04.4 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 10 01:18:22 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (1763 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.43.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.78 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE
[Desktop-packages] [Bug 1738034] Re: Muted Sound Indicator randomly remains red when no sound is playing
> That is expected behavior. It turns red only to notify user that volume is muted NOPE, because sometimes it does go back to normal without any action. It's RANDOM, and that cannot possibly be expected behavior. ** Changed in: indicator-sound (Ubuntu) Status: Invalid => Confirmed ** Changed in: ubuntu-themes (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1738034 Title: Muted Sound Indicator randomly remains red when no sound is playing Status in indicator-sound package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Mute the main Ubuntu volume 2. Play some short sound Expected behavior: Obviously you won't hear the sound. While the sound plays, the indicator should become red; then, when the sound is done playing and nothing else is playing, either immediately or after a very short period (e.g. a couple of seconds), the indicator should go back to its normal color. Observed behavior: Sometimes it behaves as expected, but sometimes it will remain red forever, until you unmute it. It's utterly random. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: indicator-sound 12.10.2+16.04.20160406-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 13 17:09:25 2017 InstallationDate: Installed on 2013-10-11 (1523 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-sound.log: (process:2339): indicator-sound-WARNING **: accounts-service-access.vala:218: unable to sync volume 0,608643 to AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface 'com.ubuntu.AccountsService.Sound' (process:2339): indicator-sound-WARNING **: accounts-service-access.vala:218: unable to sync volume 0,848633 to AccountsService: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such interface 'com.ubuntu.AccountsService.Sound' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1738034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1551515] Re: My phone's bluetooth is displayed dozens of times under the network list (wifi icon)
For fuck's sake is this how long it takes to fix high-importance bugs?? Still an issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1551515 Title: My phone's bluetooth is displayed dozens of times under the network list (wifi icon) Status in One Hundred Papercuts: Confirmed Status in NetworkManager: New Status in network-manager package in Ubuntu: Confirmed Bug description: I can hardly even start describing how screwed up this is. Have a look at the screenshot. I had seen this before and hadn't even realized that "XT1039 Network" repeated like 37 times had something to do with my own Android phone, a motorola Moto G. Needless to say I have only one. Out of curiosity I clicked on one of "them" (thinking this was some neighboor's device, obviously suspecting it was just one device repeated several times because of a bug), and then my phone vibrated prompting me whether to accept the connection from the computer. Which I did. As a result, the bluetooth indicator next to the network indicator showed a lock icon for a fraction of a second, which immediately disappeared. I guess that means that the computer and the phone peered via bluetooth for a few instants. At the same time, the wifi icon started animating (as if the computer was connecting to a wifi network... or a network of any kind I guess, since the same stupidly designed wifi-like animation is used when connecting to LAN via an ethernet cable). After that, the small lock below the bluetooth icon disappeared, the wifi icon stopped animating and went back to its normal "connected" status (I was previously and still connected to my home router's wifi network), and a baloon saying "Disconnected [NL] Network" appeared and disappeared. Then I repeated the test several times with the same result, except that the phone didn't prompt me any more to accept the connection. This is totally screwed up in several ways. First, there's no reason "XT1039 Network" should be listed AT ALL together with wifi and ethernet networks. What kind of "network" is it supposed to be?? Of course I have not turned on bluetooth tethering on the phone, and bluetooth connection to the phone is already available under the bluetooth indicator. If it makes any sense at all to show the mobile device as a "network" alongside with wifi and cable networks because, well, bluetooth is a network as well, then 1) the list of bluetooth "networks" should have a header, just like "wifi networks" and "ethernet network". Right now, there is just a list of networks that you don't know what kind they are 2) the device should be only listed once, not 37 times 3) I also suspect the 3 items called just "network" are related 4) If it is there at all, it must work. What is it supposed to do? The same as unfolding the menu under the Bluetooth indicator, hovering on the device there (which is listed only once there) and turning on the "Connection" switch? That one does work. This one (in the list of networks) doesn't. And if it is supposed to do something different, it's clearly failing as well. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.2 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 1 03:29:50 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (871 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.167 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2016-01-18 (42 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-20T16:52:59.722501 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1551515/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
> Please only send constructive comments. Here's a constructive comment: Ubuntu, as a distribution, should switch to another default file manager other than Nautilus, because Nautilus is poorly maintained and the upstream developers keep making bad design decisions that only make the software worse. Has been so for years already, and it doesn't show any signs of getting better. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1164016] Re: restore type-ahead find
> Sounds to me like those in charge of deciding the direction of gnome / > nautilus / etc. > don't really think about the users as much as they should They don't THINK much at all, let alone about the users. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774652] [NEW] xorg stopped responding to keyboard. Killing xorg "fixed" it
Public bug reported: I booted Ubuntu, and when I started using it, nothing would respond to the keyboard. Everything was responding normally to the mouse. It looked like the keystrokes were being "buffered" extremely slowly, I'll explain: For example, I opened Chrome and I started typing "facebook" in the address bar, but no character showed up, as if the keyboard wasn't even connected (however, I had used the same keyboard to type my password to log in and that had worked). So I opened a terminal, and then the characters "fa" showed up on the command line: that is two of the several characters that I had typed almost a minute before into another application. Then I started hitting keys randomly on my keyboard, like "lksjdbljb", and opening several applications (e.g. open Thunderbird, click "new message" - remember, the mouse was responding - and type random characters into the "to" address). With several seconds of delay, some other random characters that I had typed minutes before in another app would show up. That is, keyboard totally unusable, as if the keystroke buffer was slow. And this would happen with both the laptop's builtin keyboard and the external one connected via USB. I hit Ctrl+Alt+F1 (which responded immediately) to open a virtual terminal. I logged in on the virtual terminal, where the keyboard(s) would respond perfectly. I ran "top", and there was no process consuming an abnormal amount of CPU. I tried killing the "at-spi2-registr" process which was second in the list with like 2% CPU consumption and had caused me problems before (see #1772109), but that didn't help (I switched back to my xorg session via ctrl+alt+f7 and the keyboard was still berserk there). So finally I killed xorg, which obviously logged me out, and after I logged back in everything was working normally. About half of the fucking times I boot or reboot, the system is unusable due to some bug like this. Now this is a new one. Fucking pathetic. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 1 15:59:54 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (1693 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel:
[Desktop-packages] [Bug 1772109] Re: Xorg consuming 50% CPU for no good reason, at-spi2-registr another 20%, non-stop since boot
Interestingly, killing the "at-spi2-registr" process has made Xorg's CPU consumption go down to normal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1772109 Title: Xorg consuming 50% CPU for no good reason, at-spi2-registr another 20%, non-stop since boot Status in xorg package in Ubuntu: New Bug description: I have booted the computer about half an hour ago. Since the very beginning, I noticed the fan spinning at high spin so I launched "top", and noticed that Xorg was consuming about 50% CPU and another process called "at-spi2-registr" is consuming another 20%. Since then, They have continued consuming that amount of CPU constantly, all the time, whether or not I was doing anything. The only applications I opened are a terminal where I'm running top and the browser where I've been browsing Facebook. Before I launched the browser and after I closed it, CPU usage by these processed has never gone below 50% and 20% respectively. This is fucking ridiculous. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 18 22:17:40 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (1680 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 18 21:44:15 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772109/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772109] [NEW] Xorg consuming 50% CPU for no good reason, at-spi2-registr another 20%, non-stop since boot
Public bug reported: I have booted the computer about half an hour ago. Since the very beginning, I noticed the fan spinning at high spin so I launched "top", and noticed that Xorg was consuming about 50% CPU and another process called "at-spi2-registr" is consuming another 20%. Since then, They have continued consuming that amount of CPU constantly, all the time, whether or not I was doing anything. The only applications I opened are a terminal where I'm running top and the browser where I've been browsing Facebook. Before I launched the browser and after I closed it, CPU usage by these processed has never gone below 50% and 20% respectively. This is fucking ridiculous. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 18 22:17:40 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (1680 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 18 21:44:15 2018 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1772109 Title: Xorg consuming 50% CPU for no good reason, at-spi2-registr another 20%, non-stop since boot Status in xorg package in Ubuntu: New Bug description: I have booted the computer about half an hour ago. Since the very beginning, I noticed the fan spinning at high spin so I launched "top", and noticed that Xorg was consuming about 50% CPU and another process called "at-spi2-registr" is consuming another 20%. Since then, They have continued consuming that amount of CPU constantly, all the time, whether or not I was doing anything. The only applications I opened are a terminal where I'm running
[Desktop-packages] [Bug 1067520] Re: takes ages to show contents of some folders with very few files
Yes, it looks like it's most probably unrelated to the other bug you mention, but I fail to see how that leads you to conclude (or "assume") it is fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1067520 Title: takes ages to show contents of some folders with very few files Status in nautilus package in Ubuntu: Fix Released Bug description: There are a few particular folders in my filesystem which don't have anything special (that I know of) and that do _not_ contain many files or subfolder (just a dozen items), which at random times take several seconds to show up when I open them in Nautilus. Most of the times it happens when it's the first time I open that folder (since boot) or when a long time has passed since the last time I opened that folder. After that, if I exit and reenter the folder it opens fast. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.4.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu14 Architecture: i386 Date: Tue Oct 16 22:03:12 2012 GsettingsChanges: org.gnome.nautilus.window-state geometry '1249x780+117+22' org.gnome.nautilus.window-state sidebar-width 180 org.gnome.nautilus.window-state start-with-status-bar true InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to precise on 2012-05-17 (152 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1067520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1733337] Re: Randomly fails to show folder contents, "loading..." forever
I think you should stop assuming that all bugs that you don't observe, that had never been easy to systematically reproduce in the first place, are fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/177 Title: Randomly fails to show folder contents, "loading..." forever Status in nautilus package in Ubuntu: Fix Released Bug description: This happens to me randomly every once in a very long while. I don't know of a way to reproduce it systematically. I just navigate to a folder. It says "Loading..." on the bottom-right of the window, and it stays like that forever, failing to display the contents of the folder, without any error message. It doesn't have to be a folder with lots of files. Right now I've just seen it happen with a folder that only contains 4 files. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 20 15:28:13 2017 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1377x833+2463+219'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1500 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1766100] Re: Desktop keeps showing files that are no longer there
> I'm not able to reproduce this bug [...] so I'm assuming this is Fix Released You know the saying "'ass-u-me' makes an *** out of u and me..." There has never been any way to SYSTEMATICALLY reproduce the bug, I have just observed it RANDOMLY from time to time, so, you being unable to reproduce it doesn't mean it's fixed. It could be, but that's not something you can just assume. ** Changed in: nautilus (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1766100 Title: Desktop keeps showing files that are no longer there Status in nautilus package in Ubuntu: Confirmed Bug description: Hours after downloading a few pdf files with Chrome into the Desktop and being done with them, I went to delete them. I was surprised to find a file called something.pdf.chdownload. These are the temporary files that Chrome creates while downloading the files, then it renames them to their final filename without the .chrdownload suffix when they are complete. All of the files had been downloaded completely and succesfully (I had actually opened all of them) so this file shouldn't exist. And indeed, when I went to download it, I got an error "Cannot move to trash. Delete it permanently?" (this is actually stupid in the first place: the reason why I'm getting this error, it turns out, is that the file does not exist, so it makes no sense to give me the option to permanently delete it, which will fail for the exact same reason). So I chose "delete", and got an error again, that the file could not be deleted. I retried several times and finally looked at "details" and found out that the source of the error was "no such file or directory". So, the file was not there. So why the fuck was it being shown on the desktop if it was no longer there? I can assume it might happen some rare times (it's a bug anyway) that you for some reason "miss" when a file ceases existing, and hence it is still falsely visible on the desktop. But there should come a point where Nautilus "realises" the file no longer exists and stops showing it. In other words, the contents of the desktop should be "refreshed" from time to time or on certain events. And trying to delete a file, triggering an error that says that the file doesn't fucking exist, should be such a case where you refresh the information and stop showing a file that doesn't exist. It's pathetic that you keep showing it forever until I kill and restart nautilus or fucking reboot. I'm sick of reporting such idiotic bugs on Nautilus. Ubuntu, for fuck's sake, switch to some better, decently maintained file manager. Nautilus is CRAP. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114 Uname: Linux 4.4.0-119-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 22 18:04:34 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1369x817+258+98'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1653 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1766100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1759282] Re: randomly become unable to open new Nautilus windows
Importance low? You must really be retarded. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1759282 Title: randomly become unable to open new Nautilus windows Status in nautilus package in Ubuntu: Confirmed Bug description: At random times after having the system running for a few hours this starts happening: - I don't have any Nautilus window open (I previously dad and at some point closed all of them) - I click on Nautilus' launcher icon - it kind of blinks for like 30 seconds (by the way, that's barely noticeable, that sucks on its own) and then nothing happens, no Nautilus window opens up, no error message shows up (that's another thing that is wrong on its own, you should ALWAYS get an error message when something fails) and the Launcher icon finally stops blinking. I retry a few times, same result. So I open a terminal and try to launch Nautilus from there, so at least I get the fucking error messages: $ nautilus (nautilus:18764): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed (nautilus:18764): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Could not register the application: Timeout was reached (nautilus:18764): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed (nautilus:18764): GLib-GObject-WARNING **: invalid (NULL) pointer instance (nautilus:18764): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed For fuck's sake please switch to some other file manager, Nautilus is pathetic. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 27 16:03:32 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1197x691+309+248'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1627 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1759282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
