[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888934] [NEW] Indicator is shown twice
Public bug reported: See the screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: indicator-bluetooth 0.0.6+17.10.20170605-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Jul 25 12:03:34 2020 InstallationDate: Installed on 2013-10-11 (2478 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-bluetooth UpgradeStatus: Upgraded to focal on 2020-07-12 (12 days ago) ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "Screenshot from 2020-07-25 12-02-17.png" https://bugs.launchpad.net/bugs/1888934/+attachment/5395678/+files/Screenshot%20from%202020-07-25%2012-02-17.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1888934 Title: Indicator is shown twice Status in indicator-bluetooth package in Ubuntu: New Bug description: See the screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: indicator-bluetooth 0.0.6+17.10.20170605-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Jul 25 12:03:34 2020 InstallationDate: Installed on 2013-10-11 (2478 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-bluetooth UpgradeStatus: Upgraded to focal on 2020-07-12 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1888934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887407] Re: Distribution upgrade uninstalled TortoiseHG without asking me
> the upgrade gives you a chance to see the details you want. You were prompted with these screens, including the obsolete software screen, correct? Correct. As I said, not good enough. > Please be more specific about the exact changes you would like to see. Again as I said: for every individual application that you are going to remove that I installed manually (as opposed to it being installed as a dependency), you have to show an individual popup screen with a very scary warning. THEN, if you want, there you can add a checkbox like "apply to all" or whatever, where I can choose to accept in bulk after reviewing a list. OR simply change the "remove obsolete packages" prompt to make it more scary, so I get the impression that I seriously need to review the list. However, if the number is actually in the order of 86, you need to make it smaller to begin with, one way or another. Otherwise, even if I start to look at the list seriously, chances are I'll end up missing something or saying "well, whatever". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1887407 Title: Distribution upgrade uninstalled TortoiseHG without asking me Status in apt package in Ubuntu: Incomplete Bug description: I had TortoiseHG installed on my computer https://tortoisehg.bitbucket.io/download/linux.html After upgrading from Ubuntu 16.04 to 18.04, then 19.10 and then 20.04 (I can't tell at what stage), it's GONE. Never was I asked if I was fine with that. I don't care if there's a conflict of packages or whatever, you don't just uninstall software like that without asking me for confirmation. And yes, at some point I guess I clicked Yes to something like "2387 packages will be installed, 8793 will be removed" or whatever. But if you are going to uninstall an application that I installed manually (as opposed to some library that I never chose to install), you have to give a very specific warning and prompt, one that I can't easily miss. This is OUTRAGEOUS. Now I wonder how many other programs, that I don't use that often (unlike THG with which I work on a daily basis) may be gone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 13 17:55:51 2020 InstallationDate: Installed on 2013-10-11 (2466 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1887407/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1888061] [NEW] "Line by line difference" of config files during release upgrade is an unreadable mess
Public bug reported: I upgraded from 16.04 to 18.04, then to 19.10, then to 20.04. I'm not sure ini whih of the upgrades I noticed the issue but I'm pretty sure it applies to all of them. As usual, the upgrade had to install some configuration files which would replace some files I had modified, and so I got the prompt to choose what to do: whether to keep my modified version, or overwrite it with the packager's version. I don't remember the exact interface, but when you are prompted to choose that, you have a few options to see the differences between the two files. I think by default it shows a classical diff (with "+++"s and "---"s) but there is an option to show "line by line differences". I chose that for one file, and I expected to see a side-by-side diff similar to those I've seen in dozens of tools, where you see the two entire files side by side and the differences are highlighted in both sides in colors, such as lines that are added or removed and lines that are modified. Short of that, the very least that I would have expected was to show the two files side by side. Instead, this PATHETIC CRAP showed up which can be seen in the sceenshot. And don't remind me of the code of conduct. I'm not insulting anybody. It's a FACT that this is crap and that it is pathetic. Not only are DIFFERENCES not shown (line by line or otherwise). The two files are shown as one single text file, where each line of the second file is just appended to the corresponding line of the first file. You can't even tell where the line of one file begins and the line of the other ends. It's a completely useless way to show "differences" between two files. It's less useful than just showing the two files next to each other in two independent text boxes. Way less useful. Let alone compared to an actual side-by-side diff tool (and there are plenty to chose from). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Jul 18 17:30:36 2020 InstallationDate: Installed on 2013-10-11 (2471 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to focal on 2020-07-12 (5 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "Screenshot from 2020-07-11 17-25-59.png" https://bugs.launchpad.net/bugs/1888061/+attachment/5393794/+files/Screenshot%20from%202020-07-11%2017-25-59.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1888061 Title: "Line by line difference" of config files during release upgrade is an unreadable mess Status in apt package in Ubuntu: New Bug description: I upgraded from 16.04 to 18.04, then to 19.10, then to 20.04. I'm not sure ini whih of the upgrades I noticed the issue but I'm pretty sure it applies to all of them. As usual, the upgrade had to install some configuration files which would replace some files I had modified, and so I got the prompt to choose what to do: whether to keep my modified version, or overwrite it with the packager's version. I don't remember the exact interface, but when you are prompted to choose that, you have a few options to see the differences between the two files. I think by default it shows a classical diff (with "+++"s and "---"s) but there is an option to show "line by line differences". I chose that for one file, and I expected to see a side-by-side diff similar to those I've seen in dozens of tools, where you see the two entire files side by side and the differences are highlighted in both sides in colors, such as lines that are added or removed and lines that are modified. Short of that, the very least that I would have expected was to show the two files side by side. Instead, this PATHETIC CRAP showed up which can be seen in the sceenshot. And don't remind me of the code of conduct. I'm not insulting anybody. It's a FACT that this is crap and that it is pathetic. Not only are DIFFERENCES not shown (line by line or otherwise). The two files are shown as one single text file, where each line of the second file is just appended to the corresponding line of the first file. You can't even tell where the line of one file begins and the line of the other ends. It's a completely useless way to show "differences" between two files. It's less useful than just showing the two files next to each other in two independent text boxes. Way less useful. Let alone compared to an actual side-by-side diff tool (and there are plenty to chose from).
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1887574] [NEW] "The following additional packages will be installed" and "The following NEW packages will be installed"
Public bug reported: I did: $ sudo apt-get install cinnamon-desktop-environment I attach the complete output below. There are two blocks among others: The following additional packages will be installed: () The following NEW packages will be installed: () The two lists massively overlap, though they are not exactly identical. The phrasing is ambiguous to start with: even if the two lists didn't overlap at all, I would be quite confused by this message, because it's not clear what the difference is supposed to be between "additional" packages that are going to be installed and "NEW" packages that are going to be installed. That alone is an issue. But the fact that the two lists are almost (but not quite) identical, makes me wonder whether something is wrong, like a duplicate source or something. If that was the case, there should be a warning clarifying it. If all is ok, then again, the phrasing is deficient. $ sudo apt-get install cinnamon-desktop-environment Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: at gcc-9-base:i386 gir1.2-geocodeglib-1.0 gir1.2-mutter-2 gnome-software-common libaio1 libargon2-0 libatk1.0-0:i386 libavahi-common-data:i386 libavresample3 libavutil-ffmpeg54 libavutil55 libbcprov-java libboost-date-time1.65.1 libboost-filesystem1.65.1 libboost-iostreams1.65.1 libboost-locale1.65.1 libboost-program-options1.67.0 libboost-python1.65.1 libboost-regex1.65.1 libboost-signals1.65.1 libboost-system1.65.1 libboost-thread1.65.1 libbrlapi0.6 libcamel-1.2-61 libcdio17 libcommons-lang3-java libdatrie1:i386 libdns1104 libevent-2.1-6 libevent-core-2.1-6 libffi6:i386 libfl2 libfluidsynth1 libfprint0 libfribidi0:i386 libgcc-8-dev libgeos-3.6.2 libgeos-3.7.2 libgeotiff2 libgl1-mesa-glx:i386 libgmime-3.0-0 libgnome-desktop-3-17 libgraphite2-3:i386 libharfbuzz0b:i386 libhunspell-1.6-0 libidn11:i386 libip6tc0 libiptc0 libisc-export169 libisc1100 libisc1105 libisccc161 libjs-inherits libkeyutils1:i386 libkyotocabinet16v5 liblivemedia64 libllvm9 liblouis14 liblouis17 liblouisutdml8 liblwres161 libmagickcore-6.q16-3 libmicrodns0 libmng2:i386 libmutter-2-0 libmypaint-1.3-0 libmysqlclient20 libnet1 libnfs12 libomp5 libomp5-10 libopencv-core3.2 libopencv-ml3.2 libopenjpeg5 libopenobex2 liborcus-0.13-0 libpackagekit-glib2-16 libpango-1.0-0:i386 libpangox-1.0-0 libplacebo4 libpostproc54 libprocps6 libproj13 libpython3.7-minimal libqpdf21 libqscintilla2-qt5-l10n libqt5script5 libreoffice-avmedia-backend-gstreamer libreoffice-style-galaxy libruby2.5 libshiboken1.2v5 libshiboken2-5.11 libspeexdsp1:i386 libssl1.0-dev libssl1.0.0:i386 libstdc++-7-dev libswresample-ffmpeg1 libtalloc2:i386 libtevent0:i386 libthai0:i386 libusbmuxd4 libuv1-dev libva1 libvpx3 libvpx5 libwireshark12 libwiretap9 libwscodecs2 libwsutil10 libx265-146 libx265-79 libx86emu1 libxcb-dri2-0-dev libxcb-dri3-dev libxcb-glx0-dev libxcb-randr0-dev libxcb-sync-dev libxft2:i386 libxshmfence-dev libxt6:i386 libxv1:i386 node-abbrev node-ansi-regex node-aproba node-aws4 node-builtins node-call-limit node-camelcase node-chownr node-color-name node-concat-map node-cookie-jar node-core-util-is node-decamelize node-delegates node-editor node-extsprintf node-fast-deep-equal node-har-schema node-has-flag node-has-symbol-support-x node-has-to-string-tag-x node-has-unicode node-hosted-git-info node-iferr node-invert-kv node-is-object node-is-plain-obj node-is-retry-allowed node-is-stream node-isstream node-json-schema node-json-stringify-safe node-jsonparse node-lcid node-lockfile node-mime node-nopt node-opener node-path-is-inside node-process-nextick-args node-promise-inflight node-pseudomap node-punycode node-qs node-qw node-require-main-filename node-retry node-safe-buffer node-semver node-semver-diff node-signal-exit node-slash node-slide node-sorted-object node-spdx-license-ids node-string-decoder node-strip-json-comments node-text-table node-tunnel-agent node-uid-number node-unpipe node-uuid node-validate-npm-package-name node-wrappy node-xtend pastebinit pax python-certifi python-constantly python-dateutil python-idna python-pyasn1 python-simplejson python3-asn1crypto python3-pycurl python3-zope.interface qtdeclarative5-qtquick2-plugin ruby2.5 ruby2.5-dev ruby2.5-doc unity-scope-devhelp unity-scope-manpages unity-scope-tomboy unity-scope-yelp x11proto-composite-dev Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: blueman cinnamon cinnamon-common cinnamon-control-center cinnamon-control-center-data cinnamon-control-center-goa cinnamon-core cinnamon-screensaver cinnamon-session cinnamon-session-common cinnamon-settings-daemon cjs desktop-base fig2dev five-or-more fonts-noto fonts-noto-cjk-extra fonts-noto-core fonts-noto-extra fonts-noto-ui-core fonts-noto-ui-extra
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-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 Ubuntu Touch seeded 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
[Touch-packages] [Bug 1887407] [NEW] Distribution upgrade uninstalled TortoiseHG without asking me
Public bug reported: I had TortoiseHG installed on my computer https://tortoisehg.bitbucket.io/download/linux.html After upgrading from Ubuntu 16.04 to 18.04, then 19.10 and then 20.04 (I can't tell at what stage), it's GONE. Never was I asked if I was fine with that. I don't care if there's a conflict of packages or whatever, you don't just uninstall software like that without asking me for confirmation. And yes, at some point I guess I clicked Yes to something like "2387 packages will be installed, 8793 will be removed" or whatever. But if you are going to uninstall an application that I installed manually (as opposed to some library that I never chose to install), you have to give a very specific warning and prompt, one that I can't easily miss. This is OUTRAGEOUS. Now I wonder how many other programs, that I don't use that often (unlike THG with which I work on a daily basis) may be gone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 13 17:55:51 2020 InstallationDate: Installed on 2013-10-11 (2466 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1887407 Title: Distribution upgrade uninstalled TortoiseHG without asking me Status in apt package in Ubuntu: New Bug description: I had TortoiseHG installed on my computer https://tortoisehg.bitbucket.io/download/linux.html After upgrading from Ubuntu 16.04 to 18.04, then 19.10 and then 20.04 (I can't tell at what stage), it's GONE. Never was I asked if I was fine with that. I don't care if there's a conflict of packages or whatever, you don't just uninstall software like that without asking me for confirmation. And yes, at some point I guess I clicked Yes to something like "2387 packages will be installed, 8793 will be removed" or whatever. But if you are going to uninstall an application that I installed manually (as opposed to some library that I never chose to install), you have to give a very specific warning and prompt, one that I can't easily miss. This is OUTRAGEOUS. Now I wonder how many other programs, that I don't use that often (unlike THG with which I work on a daily basis) may be gone. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apt 2.0.2ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 13 17:55:51 2020 InstallationDate: Installed on 2013-10-11 (2466 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1887407/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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:
[Touch-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
[Touch-packages] [Bug 1887288] [NEW] upgrade to 19.10 seemed to finish silently with no confirmation nor error message
Public bug reported: On Ubuntu 18.04, Software Updater informed me that an upgrade to 19.10 was available, so I chose "Upgrade". The process went reasonably smoothly (except for a "system problem detected" popup at the very beginning, that happens all the time - we are talking "ubuntu" smoothly). In the "Distribution Upgrade" window, the steps "Preparing to Upgrade" and "Setting new software channels" got checked pretty quickly, then "Getting new packages" took several minutes, and then "Installing the upgrades" went on for a few hours, with the progress bar slowly but steadily growing. When the progress bar was almost full, near the end, for some reason it went back to the beginning, while still at the stage "Installing the upgrades". As if the "installing the upgrades" stage had restarted from scratch. That, alone, is a bug. But then, several minutes later, I got distracted, and when I came back, the window was gone. There was absolutely nothing on the screen regarding the upgrade process. Not an error message, not a confirmation message saying the upgrade was complete. I couldn't tell whether it was finished without any confirmation message, or if it had crashed and failed with no error message, or if it was processing something and a new window was going to pop up at any moment, without any "loading" or "wait" indicator. None of the three scenarios is acceptable. I waited a while, also I opened a terminal and had a look at running processes to see if there was something that looked like it could be upgrade-related, and couldn't find any. After several minutes of no apparent activity, I restarted. At first, the system got stuck at a black screen with a blinking cursor (just after selecting Ubuntu from the boot menu). I thought the distributioon upgrade had bricked my computer like almost every time in the past. But fortunately no. I powered it down and restarted again, and it succesfully booted to what it seems to be a fully functional 19.10 (of course, we are talking "ubuntu fully functional"). Pathetic, as usual. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apt 1.9.4ubuntu0.1 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:44:39 2020 InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to eoan on 2020-07-12 (0 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1887288 Title: upgrade to 19.10 seemed to finish silently with no confirmation nor error message Status in apt package in Ubuntu: New Bug description: On Ubuntu 18.04, Software Updater informed me that an upgrade to 19.10 was available, so I chose "Upgrade". The process went reasonably smoothly (except for a "system problem detected" popup at the very beginning, that happens all the time - we are talking "ubuntu" smoothly). In the "Distribution Upgrade" window, the steps "Preparing to Upgrade" and "Setting new software channels" got checked pretty quickly, then "Getting new packages" took several minutes, and then "Installing the upgrades" went on for a few hours, with the progress bar slowly but steadily growing. When the progress bar was almost full, near the end, for some reason it went back to the beginning, while still at the stage "Installing the upgrades". As if the "installing the upgrades" stage had restarted from scratch. That, alone, is a bug. But then, several minutes later, I got distracted, and when I came back, the window was gone. There was absolutely nothing on the screen regarding the upgrade process. Not an error message, not a confirmation message saying the upgrade was complete. I couldn't tell whether it was finished without any confirmation message, or if it had crashed and failed with no error message, or if it was processing something and a new window was going to pop up at any moment, without any "loading" or "wait" indicator. None of the three scenarios is acceptable. I waited a while, also I opened a terminal and had a look at running processes to see if there was something that looked like it could be upgrade-related, and couldn't find any. After several minutes of no apparent activity, I restarted. At first, the system got stuck at a black screen with a blinking cursor (just after selecting Ubuntu from the boot menu). I thought the distributioon upgrade had bricked my computer like almost every time in the past. But fortunately no. I powered it down and restarted again,
[Touch-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 Ubuntu Touch seeded 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
[Touch-packages] [Bug 1887277] Re: apt-get install REMOVES packages without replacing them and with barely any warning
What's invalid about this?? ** Description changed: I did: - $ sudo apt-get install ettercap-common + $ sudo apt-get install ettercap-common (by the way I don't even know what that is, but it is one of a few packages being "held back" by apt and that prevents me from upgrading from 18.04 to 20.04. Since apt itself doesn't give me a clue what to do and there doesn't seem to be a guide anywhere, I'm blindly trying stuff) - and I got: - Reading package lists... Done - Building dependency tree - Reading state information... Done - The following packages were automatically installed and are no longer required: - [...] - Use 'sudo apt autoremove' to remove them. - The following additional packages will be installed: - ettercap-graphical libcurl4 - The following packages will be REMOVED: - libcurl3 php7.2-curl virtualbox-6.0 < NOTE THIS !! - The following NEW packages will be installed: - libcurl4 - The following packages will be upgraded: - ettercap-common ettercap-graphical - 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. + Reading package lists... Done + Building dependency tree + Reading state information... Done + The following packages were automatically installed and are no longer required: + [...] + Use 'sudo apt autoremove' to remove them. + The following additional packages will be installed: + ettercap-graphical libcurl4 + The following packages will be REMOVED: + libcurl3 php7.2-curl virtualbox-6.0 < NOTE THIS !! + The following NEW packages will be installed: + libcurl4 + The following packages will be upgraded: + ettercap-common ettercap-graphical + 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. - - I didn't notice the part that said that some apparently unrelated packages, one of which I had installed manually (Virtual Box) would be removed. + I didn't notice the part that said that some apparently unrelated + packages, one of which I had installed manually (Virtual Box) would be + removed. Technically it asked me for confirmation, but it was in the middle of a bunch of other much more trivial stuff, and you can't just put "REMOVE" in caps and expect me to notice it. If an INSTALL command is going to UNINSTALL something that huge (not just a library that had been installed automatically and is no longer required, but an entire application that I installed manually!), you must give a very specific and explicit prompt (defaulting to No rather than Yes) with a gigantic warning, something like: - *** - * A T T E N T I O N * - * * - * If you proceed, the following packages will be REMOVED * - * * - * and NO SUITABLE REPLACEMENT will be installed * - * * - *** + ** + * A T T E N T I O N * + ** + * The following packages will be REMOVED* + ** + * and NO SUITABLE REPLACEMENT will be installed * + ** + ** - Are you REALLY sure you wish to continue? [y/N] + Are you REALLY sure you wish to continue? [y/N] (possibly red and blinking) - - NEVER before, in my entire life, have I ever seen an instance where "apt-get INSTALL" would REMOVE packages without at the same time replacing them with some more recent version or something, and even that is rare. + NEVER before, in my entire life, have I ever seen an instance where + "apt-get INSTALL" would REMOVE packages without at the same time + replacing them with some more recent version or something, and even that + is rare. I can't see a reason why the installation of a package would require the removal of another, unless it is to replace it with something that - superseeds it. + supersedes it. - Usually the list of stuff, that you're asked confirmation for when running "apt-get install", only includes stuff to be installed, upgraded and left untouched, never removed, so I'm used to responding "Yes" almost automatically. - - + Usually the list of stuff, that you're asked confirmation for when + running "apt-get install", only includes stuff to be installed, upgraded + and left untouched, never removed, so I'm used to responding "Yes" + almost automatically. Here's the rest of the output - - - - $ sudo apt-get install ettercap-common + $ sudo apt-get install ettercap-common
[Touch-packages] [Bug 1887277] Re: apt-get install REMOVES packages without replacing them and with barely any warning
By the way, VirtualBox is not even something I had installed with apt. I downloaded a .deb and installed it with dpkg or something. Also, I notice that the above command removed libcurl3 and installed libcurl4. That part makes sense. But then it uninstalled php7.2-curl. I guess that was because it depended on libcurl, but then if you uninstall it because you removed libcurl3 and replaced it with libcurl4, you should either find a solution to that (reinstall php7.2-curl? don't remove it in the first place? Install some more recent version that is compatible with libcurl4?? I have no idea, you are the package manager, it's your job) or at least TELL ME ABOUT IT so that I can make an informed decision. And by "tell me" I don't mean "Oh, by the way I'm also gonna remove this stuff", but "Package a will be removed because it depends on package b which will be replaced by package c, however no replacement could be found for package a", or something like that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1887277 Title: apt-get install REMOVES packages without replacing them and with barely any warning Status in apt package in Ubuntu: New Bug description: I did: $ sudo apt-get install ettercap-common (by the way I don't even know what that is, but it is one of a few packages being "held back" by apt and that prevents me from upgrading from 18.04 to 20.04. Since apt itself doesn't give me a clue what to do and there doesn't seem to be a guide anywhere, I'm blindly trying stuff) and I got: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: [...] Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ettercap-graphical libcurl4 The following packages will be REMOVED: libcurl3 php7.2-curl virtualbox-6.0 < NOTE THIS !! The following NEW packages will be installed: libcurl4 The following packages will be upgraded: ettercap-common ettercap-graphical 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. I didn't notice the part that said that some apparently unrelated packages, one of which I had installed manually (Virtual Box) would be removed. Technically it asked me for confirmation, but it was in the middle of a bunch of other much more trivial stuff, and you can't just put "REMOVE" in caps and expect me to notice it. If an INSTALL command is going to UNINSTALL something that huge (not just a library that had been installed automatically and is no longer required, but an entire application that I installed manually!), you must give a very specific and explicit prompt (defaulting to No rather than Yes) with a gigantic warning, something like: *** * A T T E N T I O N * * * * If you proceed, the following packages will be REMOVED * * * * and NO SUITABLE REPLACEMENT will be installed * * * *** Are you REALLY sure you wish to continue? [y/N] (possibly red and blinking) NEVER before, in my entire life, have I ever seen an instance where "apt-get INSTALL" would REMOVE packages without at the same time replacing them with some more recent version or something, and even that is rare. I can't see a reason why the installation of a package would require the removal of another, unless it is to replace it with something that superseeds it. Usually the list of stuff, that you're asked confirmation for when running "apt-get install", only includes stuff to be installed, upgraded and left untouched, never removed, so I'm used to responding "Yes" almost automatically. Here's the rest of the output - $ sudo apt-get install ettercap-common Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: gdal-data libaec0 libaio1 libarmadillo8 libarpack2 libcharls1 libdap25 libdapclient6v5 libepsilon1 libfreexl1 libfyba0 libgeos-3.6.2 libgeos-c1v5 libgeotiff2 libgsasl7 libhdf4-0-alt libhdf5-100 libieee1284-3:i386 libkmlbase1 libkmldom1 libkmlengine1 libkyotocabinet16v5 libminizip1 libnetcdf13 libntlm0 libogdi3.2 libopencv-core3.2 libopencv-imgproc3.2 libopencv-ml3.2 libopencv-video3.2 libproj12 libqhull7 libsdl-ttf2.0-0 libsocket++1
[Touch-packages] [Bug 1887277] [NEW] apt-get install REMOVES packages without replacing them and with barely any warning
Public bug reported: I did: $ sudo apt-get install ettercap-common (by the way I don't even know what that is, but it is one of a few packages being "held back" by apt and that prevents me from upgrading from 18.04 to 20.04. Since apt itself doesn't give me a clue what to do and there doesn't seem to be a guide anywhere, I'm blindly trying stuff) and I got: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: [...] Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ettercap-graphical libcurl4 The following packages will be REMOVED: libcurl3 php7.2-curl virtualbox-6.0 < NOTE THIS !! The following NEW packages will be installed: libcurl4 The following packages will be upgraded: ettercap-common ettercap-graphical 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. I didn't notice the part that said that some apparently unrelated packages, one of which I had installed manually (Virtual Box) would be removed. Technically it asked me for confirmation, but it was in the middle of a bunch of other much more trivial stuff, and you can't just put "REMOVE" in caps and expect me to notice it. If an INSTALL command is going to UNINSTALL something that huge (not just a library that had been installed automatically and is no longer required, but an entire application that I installed manually!), you must give a very specific and explicit prompt (defaulting to No rather than Yes) with a gigantic warning, something like: *** * A T T E N T I O N * * * * If you proceed, the following packages will be REMOVED * * * * and NO SUITABLE REPLACEMENT will be installed * * * *** Are you REALLY sure you wish to continue? [y/N] (possibly red and blinking) NEVER before, in my entire life, have I ever seen an instance where "apt-get INSTALL" would REMOVE packages without at the same time replacing them with some more recent version or something, and even that is rare. I can't see a reason why the installation of a package would require the removal of another, unless it is to replace it with something that superseeds it. Usually the list of stuff, that you're asked confirmation for when running "apt-get install", only includes stuff to be installed, upgraded and left untouched, never removed, so I'm used to responding "Yes" almost automatically. Here's the rest of the output - $ sudo apt-get install ettercap-common Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: gdal-data libaec0 libaio1 libarmadillo8 libarpack2 libcharls1 libdap25 libdapclient6v5 libepsilon1 libfreexl1 libfyba0 libgeos-3.6.2 libgeos-c1v5 libgeotiff2 libgsasl7 libhdf4-0-alt libhdf5-100 libieee1284-3:i386 libkmlbase1 libkmldom1 libkmlengine1 libkyotocabinet16v5 libminizip1 libnetcdf13 libntlm0 libogdi3.2 libopencv-core3.2 libopencv-imgproc3.2 libopencv-ml3.2 libopencv-video3.2 libproj12 libqhull7 libsdl-ttf2.0-0 libsocket++1 libspatialite7 libsuperlu5 libsz2 liburiparser1 linux-image-4.4.0-142-generic mailutils-common odbcinst odbcinst1debian2 proj-bin proj-data Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ettercap-graphical libcurl4 The following packages will be REMOVED: libcurl3 php7.2-curl virtualbox-6.0 The following NEW packages will be installed: libcurl4 The following packages will be upgraded: ettercap-common ettercap-graphical 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. Need to get 1.178 kB of archives. After this operation, 248 MB disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 ettercap-graphical amd64 1:0.8.2-10build4 [193 kB] Get:2 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 ettercap-common amd64 1:0.8.2-10build4 [771 kB] Get:3 http://es.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libcurl4 amd64 7.58.0-2ubuntu3.9 [214 kB] Fetched 1.178 kB in 1s (1.531 kB/s) (Reading database ... 329793 files and directories currently installed.) Removing virtualbox-6.0 (6.0.22-137980~Ubuntu~xenial) ... (Reading database ... 328959 files and directories currently installed.) Preparing to unpack .../ettercap-graphical_1%3a0.8.2-10build4_amd64.deb ... Unpacking ettercap-graphical (1:0.8.2-10build4) over (1:0.8.2-2ubuntu1.16.04.1) ... Preparing to unpack
[Touch-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 Ubuntu Touch seeded 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:
[Touch-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 Ubuntu Touch seeded 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:
[Touch-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
[Touch-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
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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
[Touch-packages] [Bug 1451186] Re: "This problem was already reported..."
> If this is still an issue on a maintained version of Ubuntu please let us know. No, you let us know if this is confirmed to be fixed in more recent versions of Ubuntu, and if so, then close as fixed. ** Changed in: apport (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1451186 Title: "This problem was already reported..." Status in apport package in Ubuntu: New Bug description: Something crashed (as always) after installing Ubuntu updates, presumably due to https://bugs.launchpad.net/ubuntu/+source/nvidia- graphics-drivers-331/+bug/1268257 A popup appeared (as usual) telling me that a problem was detected and whether I wanted to report, to which I said Yes. Then, this message appeared (see screenshot), which says "The problem was already reported in the bug report DISPLAYED IN THE WEB BROWSER..." No bug report was open in the browser. I waited more than a minute and no bug report was being opened in the browser. Only after clicking on Close, did the browser finally open the related bug report. So either: 1) this is by design, that is, the bug report is supposed to be opened after closing the popup. If this is the case then => the message should be rephrased, to read "in the bug report that WILL be displayed in the web browser", and instead of Close the button should read Continue or Ok. or 2) the bug report is supposed to be opened at the same time the popup is displayed, but it takes long. If this is the case, then 2.a => either the message should read "in the bug report that IS BEING LOADED in the web browser (this may take a few minutes)", OR much better 2.b => a first popup should inform you that the bug report is being opened in the browser, with a loading/waiting indicator, and then, when it is loaded, the final message similar to the one currently displayed, should be displayed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.10 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportLog: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CrashReports: 640:0:110:33136:2015-05-03 14:52:36.419100999 +0200:2015-05-03 14:52:37.419100999 +0200:/var/crash/nvidia-331.0.crash 600:106:110:0:2015-05-03 14:52:39.567100861 +0200:2015-04-27 16:38:24.687981219 +0200:/var/crash/nvidia-331.0.uploaded 640:1000:110:1018542:2015-05-01 11:41:36.971999876 +0200:2015-05-01 11:42:00.869033693 +0200:/var/crash/_usr_bin_compiz.1000.crash 644:0:110:0:2015-05-03 14:52:38.143100920 +0200:2015-05-03 14:52:38.143100920 +0200:/var/crash/nvidia-331.0.upload CurrentDesktop: Unity Date: Sun May 3 14:53:47 2015 InstallationDate: Installed on 2013-10-11 (568 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-05-24 (343 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1451186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is
[Touch-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 Ubuntu Touch seeded 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
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
Yeah right. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794826] [NEW] Nonsense (and/or undocumented) "clean:" before filename in grep output
Public bug reported: It has started happening to me recently, than when I do: > grep -R something besides the normal expected output which is of the form: filename: match filename: match ... I also get some lines like this: clean:filename: match where the word "clean" appears literally. The matches that are shown in this form also appear in the normal form without the "clean:" prefix, so in total they show up twice. And I have checked that I have no files whose filename actually starts with "clean:" I have checked the manpage for grep and there's no occurrence of the word "clean", so if that "clean:" is supposed to actually mean something (besides being counterintuitive and being a shitty inconsistent format, and besides the fact it wouldn't make sense to show the matches twice), it's not documented. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: grep 2.25-1~16.04.1 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 27 17:43:46 2018 InstallationDate: Installed on 2013-10-11 (1811 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: grep UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grep (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1794826 Title: Nonsense (and/or undocumented) "clean:" before filename in grep output Status in grep package in Ubuntu: New Bug description: It has started happening to me recently, than when I do: > grep -R something besides the normal expected output which is of the form: filename: match filename: match ... I also get some lines like this: clean:filename: match where the word "clean" appears literally. The matches that are shown in this form also appear in the normal form without the "clean:" prefix, so in total they show up twice. And I have checked that I have no files whose filename actually starts with "clean:" I have checked the manpage for grep and there's no occurrence of the word "clean", so if that "clean:" is supposed to actually mean something (besides being counterintuitive and being a shitty inconsistent format, and besides the fact it wouldn't make sense to show the matches twice), it's not documented. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: grep 2.25-1~16.04.1 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 27 17:43:46 2018 InstallationDate: Installed on 2013-10-11 (1811 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: grep UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1794826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787225] [NEW] systemctl disable apache2 does nothing
Public bug reported: I installed apache2 on Ubuntu 16.04, and out of the box it was enabled as a service, meaning it would automatically start at every boot. That is not what I want as this is my personal computer, not a server. $ systemctl is-enabled apache2.service enabled So I ran: $ sudo systemctl disable apache2 and this was the output: apache2.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install disable apache2 insserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6). insserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6). Then I rebooted. I expected to find apache2 not running. Instead, it was running. Surprisingly: $ systemctl is-enabled apache2.service apache2.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install is-enabled apache2 disabled so, it shows up as disabled, yet it is started at startup. I wonder if this is what those warnings were about. Those messages are unclear as fuck, I have no f***ing clue what they are supposed to mean. I read that the CURRENT runlevel overrides a DEFAULT. I guess that should be fine, unless what systemctl actually changes are the defaults, and those are overwritten by something else, which means that "sysctl disable" will have no effect. If that is the case, then the warning should be more explicit: - be specific about the fact that "LSB defaults" are what the command is changing - tell me that as a result, the services will not be disabled - tell me WHAT is overriding the defaults that I'm attempting to change - and/or tell me what I am supposed to do to fix the issue ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21.4 ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 Uname: Linux 4.4.0-133-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 15 16:26:28 2018 InstallationDate: Installed on 2013-10-11 (1768 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: systemd 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 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1787225 Title: systemctl disable apache2 does nothing Status in systemd package in Ubuntu: New Bug description: I installed apache2 on Ubuntu 16.04, and out of the box it was enabled as a service, meaning it would automatically start at every boot. That is not what I want as this is my personal computer, not a server. $ systemctl is-enabled apache2.service enabled So I ran: $ sudo systemctl disable apache2 and this was the output: apache2.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install disable apache2 insserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6). insserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6). Then I rebooted. I expected to find apache2 not running. Instead, it was running. Surprisingly: $ systemctl is-enabled apache2.service apache2.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install is-enabled apache2 disabled so, it shows up as disabled, yet it is started at startup.
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786625] Re: "find" command throws nonsense error message
It's funny that when creating the bug report there was a choice for the package
to report against:
- linux
- I don't know.
I chose "I don't know", but it has been assigned to linux allthesame.
Brilliant.
** Also affects: findutils (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to findutils in Ubuntu.
https://bugs.launchpad.net/bugs/1786625
Title:
"find" command throws nonsense error message
Status in findutils package in Ubuntu:
New
Bug description:
Steps to reproduce:
1. Run this command from a terminal:
$ find . -name *.txt
Expected result:
It should list all the files found in the current directory or any descendant
directory whose name ends in ".txt". It may or may not find matching files,
depending on whether there are or there aren't.
If there's something wrong in my command, then it should ALWAYS consistently
issue a sensible error message explaining what's wrong with my command, and
that should happen regardless of the contents of the current directory.
Observed results:
If there are no .txt files to be found, it behaves as expected (i.e., no
results, no error message).
If there are files ending in .txt, sometimes it behaves as expected, showing
the results.
If, however, there are files ending in ".txt" with dashes ("-") or spaces ("
") in the filename, AND there is more than one file that matches the criteria,
then it displays this completely nonsensical error message:
find: paths must precede expression: .txt
Usage: find [-H] [-L] [-P] [-Olevel] [-D
help|tree|search|stat|rates|opt|exec|time] [path...] [expression]
where "X.txt" is an actual filename of a matching file.
For example, this will reproduce the issue:
$ echo "lalala" > aaa.txt
$ echo "lololo" > foo-bar.txt
$ find . -name *.txt
find: paths must precede expression: foo-bar.txt
Usage: find [-H] [-L] [-P] [-Olevel] [-D
help|tree|search|stat|rates|opt|exec|time] [path...] [expression]
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-131-generic 4.4.0-131.157
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
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo2898 F pulseaudio
CurrentDesktop: Unity
Date: Sat Aug 11 17:30:54 2018
HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3
InstallationDate: Installed on 2013-10-11 (1764 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: Acer Aspire V3-571G
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-131-generic N/A
linux-backports-modules-4.4.0-131-generic N/A
linux-firmware 1.157.20
SourcePackage: linux
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1786625/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 958661] Re: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings
prompt on the phone (i.e. source device)
** Attachment added: "photo_2018-07-24_12-08-07.jpg"
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+attachment/5167082/+files/photo_2018-07-24_12-08-07.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/958661
Title:
"Receive files over bluetooth" randomly stops working - plus setting
should be available under BlueTooth settings
Status in bluez package in Ubuntu:
Confirmed
Bug description:
I often send image files via bluetooth from my android phone to my
ubuntu PC.
It worked fine until yesterday, but now I systematically get "the
remote bluetooth device rejected the request".
Nothing has changed in the way I transfer files and I'm trying from
the very same phone.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-16-generic 3.0.0-16.29
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo 32650 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 25
Simple ctrls : 16
Date: Sun Mar 18 17:55:36 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.0.0-16-generic N/A
linux-backports-modules-3.0.0-16-generic N/A
linux-firmware1.60.1
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 958661] Re: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings
Now, several minutes after turning on Bluetooth on the computer, it was
finally visible from the phone.
So from the phone I tried sending a file, and I got the screen (on the phone)
that I attached.
It said: "Type the pairing code then press Return or Enter". (note: "the"
pairing code. What pairing code? If I am supposed to type it on the computer,
which "press return or enter" seems to suggest, then it should show up on the
phone - or viceversa)
So on the computer some prompt was supposed to show up, but it didn't. A
small padlock showed up in the bluetooth icon on the computer, but there
was no prompt for a code anywhere, nor did it show up by clicking on the
bluetooth icon.
After a while the operation timed out from the phone.
Then I tried again.
This time, at the prompt "type the pairing code then press Return or Enter"
(again the one in the screenshot) I tapped on "pair". (the prompt is quite
ambiguous: am I supposed to type the code, which I can't possibly know, in
which case the "pair" button shouldn't be necessary, or should I press "pair"
and *then* I'll be shown the code on the phone and prompted to insert it on the
computer, in which case the message is confusing because it's telling me to
enter it now??)
So I tapped on "pair", and... The file was sent succesfully!! No code showed up
anywhere and I didn't have to insert it anywhere.
Of course I had paired these two particular devices before, literally years ago
(and I'm not abusing the word "literally").
The UI of the whole process is a fucking mess on both sides, both Ubuntu
AND Android. There are a bunch of bugs on both sides. Sharing files via
bluetooth is a hell.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/958661
Title:
"Receive files over bluetooth" randomly stops working - plus setting
should be available under BlueTooth settings
Status in bluez package in Ubuntu:
Confirmed
Bug description:
I often send image files via bluetooth from my android phone to my
ubuntu PC.
It worked fine until yesterday, but now I systematically get "the
remote bluetooth device rejected the request".
Nothing has changed in the way I transfer files and I'm trying from
the very same phone.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-16-generic 3.0.0-16.29
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo 32650 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 25
Simple ctrls : 16
Date: Sun Mar 18 17:55:36 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.0.0-16-generic N/A
linux-backports-modules-3.0.0-16-generic N/A
linux-firmware1.60.1
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 958661] Re: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings
Also, in "Personal File Sharing Preferences" (it's ridiculous that you
have to look for these settings somewhere else, they should be under
Bluetooth settings), "receive files over bluetooth" is turned on and
"accept files" is set to "always".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/958661
Title:
"Receive files over bluetooth" randomly stops working - plus setting
should be available under BlueTooth settings
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I often send image files via bluetooth from my android phone to my
ubuntu PC.
It worked fine until yesterday, but now I systematically get "the
remote bluetooth device rejected the request".
Nothing has changed in the way I transfer files and I'm trying from
the very same phone.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-16-generic 3.0.0-16.29
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo 32650 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 25
Simple ctrls : 16
Date: Sun Mar 18 17:55:36 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.0.0-16-generic N/A
linux-backports-modules-3.0.0-16-generic N/A
linux-firmware1.60.1
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 958661] Re: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings
On 16.04, now I can't even see the computer from another bluetooth
device (my smartphone).
Bluetooth is turned on and visibility is turned on. If I click on
"ubuntu settings..." there is no other setting (I thought maybe there
was something like "discoverability" that I should turn on).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/958661
Title:
"Receive files over bluetooth" randomly stops working - plus setting
should be available under BlueTooth settings
Status in bluez package in Ubuntu:
Incomplete
Bug description:
I often send image files via bluetooth from my android phone to my
ubuntu PC.
It worked fine until yesterday, but now I systematically get "the
remote bluetooth device rejected the request".
Nothing has changed in the way I transfer files and I'm trying from
the very same phone.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-16-generic 3.0.0-16.29
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo 32650 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 25
Simple ctrls : 16
Date: Sun Mar 18 17:55:36 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.0.0-16-generic N/A
linux-backports-modules-3.0.0-16-generic N/A
linux-firmware1.60.1
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738034] Re: Muted Sound Indicator randomly remains red when no sound is playing
> You keep saying these random behaviors. But I am unable to > reproduce any of them on 18.04 & 18.10. Can you explain, how to reproduce in > a concise way? If there was a reliable way of reproducing it, it wouldn't be random. Here's what happens to me: CASE 1: - I mute the volume when no sound is playing Expected behavior: the icon shouldn't go red Observed behavior: usually the icon doesn't go red, but sometimes it does. Then sometimes it remains red until I unmute, sometimes it goes back to normal a few seconds later CASE 2: - I mute the volume - I start playing a sound (e.g. a youtube video or whatever), or some sound starts playing (e.g. a Facebook notification in a browser's tab). Expected behavior: according to you, the icon should become red and remain so until you manually unmute the volume. That's nonsense. What's the logic behind that? Why would I need a reminder that at some point a sound played? Why is a "specific user action required"? Why should I unmute the volume after the sound has already stopped playing? To me, the expected behavior is that the icon should become red and only remain so while some sound is playing, and then go back to normal. It's useful to know when some sound IS playing and I am not hearing it because my volume is muted. When no sound is no longer playing, there's no use in knowing that at some point there had been a sound playing. But whatever the expected behavior is, the observed behavior is that sometimes the icon goes back to normal after the sound stops playing without any action on my part, while sometimes it remains red until I unmute the volume. > But I am unable to reproduce any of them on 18.04 & 18.10 I don't know, maybe it's fixed on those versions. I'm using 16.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738034] Re: Muted Sound Indicator randomly remains red when no sound is playing
> sound indicator couldn't possibly cover all scenarios why music has stopped playing It can easily do so. It can become red when the amplitude of the output waveform is non-zero and volume is muted, and go back to normal when either the amplitude of the output goes to zero or the volume is unmuted. THAT is the expected behavior. Or, if the expected behavior was really the one you describe (only go back to normal when unmuted), which would be pretty useless, then it does not work either, because, as I said, it behaves randomly. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738034] Re: Muted Sound Indicator randomly remains red when no sound is playing
Oh, and by the way, often it does not even become red in the first place when some sound starts playing while the volume is muted. Both becoming red and going back to normal are COMPLETELY UTTERLY RANDOM. (or there's some logic behind it that is so convoluted that it is incomprehensible and renders the "feature" of becoming red, to notify you of something, completely useless) -- You received this bug notification because you are a member of Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738034] Re: Muted Sound Indicator randomly remains red when no sound is playing
Sorry for my deleted comment, since you said "it's most likely THE issue with..." I thought you were referring to some specific issue that you failed to mention. I assume you meant "most likely AN issue with". Anyway, The icon is EXPECTED to become red when a sound plays and the volume is muted. The issue is that the icon doesn't go back to normal and REMAINS red when the sound is finished playing. I find it hard to believe this is an issue with an theme, are you sure it is? -- You received this bug notification because you are a member of Ubuntu Touch seeded 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: Invalid Status in ubuntu-themes package in Ubuntu: New 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738034] Re: Muted Sound Indicator randomly remains red when no sound is playing
The icon is EXPECTED to become red when a sound plays and the volume is muted. The issue is that the icon doesn't go back to normal and REMAINS red when the sound is finished playing. I find it hard to believe this is an issue with an icon-theme, but if that is the case, could you please point to where that supposed issue is described? It doesn't make sense to mark this bug as invalid. If it is a duplicate of some other bug, mark it as such, otherwise this is a bug that is not fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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: Invalid Status in ubuntu-themes package in Ubuntu: New 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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:
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
> Anyway I did, like yesterday, and it got closed > (can't find it right now [...]) Here: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1754069 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
"not so well developed/maintained"? You mean worse than Nautilus?? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759714] [NEW] Xorg suddenly starts to consume 100% CPU, apparently triggered by Chrome
Public bug reported: 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 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: Thu Mar 29 00:45:01 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)
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
> If that is genuinely the reason (and this bug has been marked as "Fix > Released" > since Jan 2014, so it seems correct), then is it not time to raise a new bug? Maybe (though it seems a little stupid to raise a new bug for exactly the same issue). Anyway I did, like yesterday, and it got closed (can't find it right now, I don't know what's wrong with the search engine of this stupid bug tracker) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
@109 this is already known to be the wrong behavior. It was introduced long ago by the hopelessly stupid Nautilus people, and patched by Ubuntu to reestablish the old sensible behavior, but something must have gone wrong in the latest release and so the idiocy has resurfaced. What I don't understand is how it can be taking so long to fix again. Oh I see why: most of us cannot change back the status of the bug once it has been changed to "fix released" (which is stupid, too). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1746752] Re: switch-screen key has stopped working
*** This bug is a duplicate of bug 1731294 *** https://bugs.launchpad.net/bugs/1731294 Oh, I'm afraid this is just a duplicate of the annoying #1731294 ** This bug has been marked a duplicate of bug 1731294 Keyboard shortcuts stop working; restarting unity-settings-daemon fixes them -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1746752 Title: switch-screen key has stopped working Status in xorg package in Ubuntu: New Bug description: I often connect an external monitor to my laptop and, when I do, I use it as the only screen, with the built-in display turned off. This is the configuration I manually set a long time ago, and there was a time when, by plugging in the screen, or bootin with the screen already connected, it would automatically switch to this configuration, as one would expect. Then Ubuntu fucked things up as it usually do at every update, so the behavior when plugging in the screen or booting became utterly random, but until now, I would always be able to switch screen configurations with the hardware keyboard shortcut (on my laptop it's fn+F6) until I get the desired one (built-in screen turned off, external screen as the only one). Actually there's usually an interval of time while the system is finishing the boot process (which takes several minutes because, you know, Ubuntu) during which the hardware switch-screen key wouldn't work properly, just switching the built-in screen on and off (immediately) without properly switching configurations. But then, when everything is up and running, it would start working as expected properly switching among different screen configurations (only built-in; builtin+external in extended desktop; mirrored; external only)... except that it would frantically switch several times for all the times you had been trying while finishing booting. That makes me think that the keyboard shortcut is handled by hardware and is just a hard on-off switch for the builtin display until something in the OS is up and running and starts handling it. Now, this was the usual behavior until now. It's pathetic in may ways, but that's not the bug I'm reporting. Now instead, after completing the boot, the screens came up as mirrored, and the hardware switch-screens key wouldn't work (it would just turn the builtin screen on and off while leaving the external screen at the same shitty resolution as a mirror of the builtin one), just like it usually happens for the first few minutes, except this time it kept (not)working this way. I had to manually go to Display settings, turn off mirror mode, switch the builtin screen off, AND adjust the external screen resolution to a non-idiotic value. And the hardware key still does nothing (not even turn on and off the builtin screen which remains off). I don't know if this issue will disappear at the next boot. I'm quite confident that it will, but that doesn't make the issue any less of a bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-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.102 Mon Jan 16 13:06:29 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.13 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 Feb 1 16:18:03 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 (1573 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade
[Touch-packages] [Bug 1746752] [NEW] switch-screen key has stopped working
Public bug reported: I often connect an external monitor to my laptop and, when I do, I use it as the only screen, with the built-in display turned off. This is the configuration I manually set a long time ago, and there was a time when, by plugging in the screen, or bootin with the screen already connected, it would automatically switch to this configuration, as one would expect. Then Ubuntu fucked things up as it usually do at every update, so the behavior when plugging in the screen or booting became utterly random, but until now, I would always be able to switch screen configurations with the hardware keyboard shortcut (on my laptop it's fn+F6) until I get the desired one (built-in screen turned off, external screen as the only one). Actually there's usually an interval of time while the system is finishing the boot process (which takes several minutes because, you know, Ubuntu) during which the hardware switch-screen key wouldn't work properly, just switching the built-in screen on and off (immediately) without properly switching configurations. But then, when everything is up and running, it would start working as expected properly switching among different screen configurations (only built-in; builtin+external in extended desktop; mirrored; external only)... except that it would frantically switch several times for all the times you had been trying while finishing booting. That makes me think that the keyboard shortcut is handled by hardware and is just a hard on-off switch for the builtin display until something in the OS is up and running and starts handling it. Now, this was the usual behavior until now. It's pathetic in may ways, but that's not the bug I'm reporting. Now instead, after completing the boot, the screens came up as mirrored, and the hardware switch-screens key wouldn't work (it would just turn the builtin screen on and off while leaving the external screen at the same shitty resolution as a mirror of the builtin one), just like it usually happens for the first few minutes, except this time it kept (not)working this way. I had to manually go to Display settings, turn off mirror mode, switch the builtin screen off, AND adjust the external screen resolution to a non-idiotic value. And the hardware key still does nothing (not even turn on and off the builtin screen which remains off). I don't know if this issue will disappear at the next boot. I'm quite confident that it will, but that doesn't make the issue any less of a bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-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.102 Mon Jan 16 13:06:29 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.13 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 Feb 1 16:18:03 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 (1573 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-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.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2:
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
Fucking unbelievable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1680750] Re: pm-hibernate does nothing at all
> 1. It sounds like this used to work? Was it working on 16.04 and only recently broke? I'm not sure. Sometimes it works, sometimes it doesn't. When it doesn't work, it won't until the next reboot. And I'm not sure it didn't happen before. It may have been less frequent for "random" reasons. Or it *may* have broken recently, I don't know. Hibernation has NEVER worked well (I guess that's why it is not made readily available through the main menu), it has a number of other issues. I AM using 16.04 right now. > 2. What model is your hardware? Acer Aspire V3-571G > 3. Did you recently update the system BIOS? Nope > Are you running the latest? No, because I would need Windows to update it. $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date V2.07 10/15/2012 ** Changed in: pm-utils (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1680750 Title: pm-hibernate does nothing at all Status in pm-utils package in Ubuntu: Confirmed Bug description: I have run from a command line: # sudo pm-hibernate and NOTHING f***ing happens. Usually it works (except for lots of issues on resume), but now I have tried it twice and it does nothing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: powerman (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 7 10:47:47 2017 InstallationDate: Installed on 2013-10-11 (1273 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: powerman UpgradeStatus: Upgraded to xenial on 2016-12-11 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1680750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671522] [NEW] display settings randomly reset
Public bug reported: I usually connect an external monitor to my laptop. I had it set up (System Settings->Displays) so that the laptop's built-in monitor is turned off, and the external monitor is the only active one (of course, when I unplug the external monitor, the builtin one turns on automatically, and it turns off when I plug in the external monitor again). I have been using this configuration for ages and it usually gets remembered across boots, as expected. Today I booted and the two monitors were both turned on, acting as an extended desktop. Unplugging and plugging the monitor again did not fix the issue. I had to manually edit the settings to put them as they were before. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-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.101 Thu Dec 1 15:52:31 PST 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". [[0;32m OK [0m] Started LSB: daemon to balance interrupts for SMP systems. 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 9 16:24:03 2017 DistUpgraded: 2016-12-11 22:45:13,519 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: 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 (1244 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-12-11 (87 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.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-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.2 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: Thu Mar 9 16:21:28 2017 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.2 ** 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 Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1671522 Title: display settings randomly reset Status in xorg package in Ubuntu: New Bug description: I usually connect an external monitor to my laptop. I had it set up
[Touch-packages] [Bug 1669581] [NEW] no screen turned on after resume from hibernation
Public bug reported: Steps to reproduce: - I connected an external monitor to my laptop through the HDMI port - my display settings are set to use only the external monitor when it is connected, so the laptop's builtin screen was turned off - I hibernated - I brought my laptop home, connected it to another external monitor through the VGA port, and resumed from hibernation Expected: the external monitor should turn on. If no external monitor is connected, then the builtin should turn on. Whenever a monitor is available, it must be made sure that at least one monitor is ALWAYS turned on no matter what. Observed: neither the builtin NOR the external monitor turned on. This is SO FUCKING STUPID. Both screens were turned off. Additionally, even unplugging and plugging the monitor (several times) did nothing. Which is even more retarded. I could verify that the system was actually up and running by hitting CTRL+ALT+T (to open a terminal) and blindly typing "sudo suspend" and entering the password: the computer actually suspended. Even after resuming from suspend, no screen turned on. I had no way to recover and I was forced to shut down, losing all my unsaved data. This does NOT always happen, but this is not the first time either. It seems to be random. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-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.101 Thu Dec 1 15:52:31 PST 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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 2 21:38:20 2017 DistUpgraded: 2016-12-11 22:45:13,519 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: 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 (1238 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-12-11 (80 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.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-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.2 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: Thu Mar 2 21:36:18 2017 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.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu
[Touch-packages] [Bug 1649155] [NEW] empty "crash report" window
Public bug reported: After fixing a broken upgrade as per bug 1649153, I rebooted, and a few "Crash report" popups (like 3 or 4). One of them was like this: see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportLog: ERROR: apport (pid 9256) Sun Dec 11 23:07:25 2016: called for pid 2019, signal 11, core limit 0 ERROR: apport (pid 9256) Sun Dec 11 23:07:25 2016: executable was modified after program start, ignoring ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 11 23:40:05 2016 InstallationDate: Installed on 2013-10-11 (1157 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to xenial on 2016-12-11 (0 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "Screenshot from 2016-12-11 23-14-20.png" https://bugs.launchpad.net/bugs/1649155/+attachment/4790502/+files/Screenshot%20from%202016-12-11%2023-14-20.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1649155 Title: empty "crash report" window Status in apport package in Ubuntu: New Bug description: After fixing a broken upgrade as per bug 1649153, I rebooted, and a few "Crash report" popups (like 3 or 4). One of them was like this: see attached screenshot ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportLog: ERROR: apport (pid 9256) Sun Dec 11 23:07:25 2016: called for pid 2019, signal 11, core limit 0 ERROR: apport (pid 9256) Sun Dec 11 23:07:25 2016: executable was modified after program start, ignoring ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 11 23:40:05 2016 InstallationDate: Installed on 2013-10-11 (1157 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to xenial on 2016-12-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1649155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1649154] [NEW] distribution upgrade wiped screen settings
Public bug reported: I think the exact same thing happened with the previous upgrade. I have a laptop and I often connect an external monitor. I had it set up so that when I connect it, the laptop's builtin display turns off and the external one works as the only display. I upgraded from 15.10 to 16.04, and the screen configuration was lost. When I connected the external monitor, the two displays were working as extended desktop (or whatever is called). I had to set up the displays again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-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.98 Mon Sep 19 17:31:03 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.2 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 Dec 11 23:17:37 2016 DistUpgraded: 2016-12-11 22:45:13,519 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: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.2.0-42-generic, x86_64: installed bbswitch, 0.8, 4.4.0-53-generic, x86_64: installed nvidia-340, 340.98, 4.2.0-42-generic, x86_64: installed nvidia-340, 340.98, 4.4.0-53-generic, x86_64: installed vboxhost, 4.3.14: added 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 (1157 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-12-11 (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.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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: Sun Dec 11 23:09:33 2016 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.2 ** 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 Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1649154 Title: distribution upgrade wiped screen settings Status in xorg package in Ubuntu: New Bug description: I think the exact same thing happened with the previous upgrade. I have a laptop and I often connect an external monitor. I had it set up so that when I connect it, the laptop's builtin display turns off and the external one works as the only
[Touch-packages] [Bug 1649153] [NEW] upgrade from 15.10 to 16.04 broken, bricks computer
Public bug reported:
I upgraded (or tried to) from 15.10 to 16.04.
After a few errors as per bug 1561467 and a few crash-report popups
which I don't know whether were related or not, I finally got the error
message:
"Could not install the upgrades
The upgrade has aborted. YOUR SYSTEM COULD BE IN AN UNUSABLE STATE. A recovery
will run now (dpkg --configure -a)"
(emphasys added).
By clicking "Close", I expedted the "recovery" to run and hopefully recover
something, but nothing happened.
Almost immediately, the upgrade window with the checklist ("download stuff",
"install stuff", ... "cleanup", "restart computer") disappeared (without
prompting me to restart the computer) and I got a message like "Upgrade
complete. The system was updated but there were errors" or something like that.
(obviously this is all unacceptable: you tell me my system could be unusable
and don't give me a clue about what the fuck happened and what I am supposed to
do?!?)
So, I tried running "dpkg --configure -a" in a terminal, but I only got
a very long series of almost identical errors regarding dependency
problems for many many packages, which ended more or less like
"Aborting, too many errors".
After a bit of googling, I tried this which I seemed to understand could maybe
fix the issue:
sudo apt-get -f install
(or "sudo apt-get install -f", can't remember now)
This seems to have worked. I could reboot (got a couple of crash reports, I
hope they won't pop up at every reboot), my system is now 16.04 and tried some
random stuff which seems to work.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.15
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.2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Dec 11 23:17:12 2016
InstallationDate: Installed on 2013-10-11 (1157 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: apt
UpgradeStatus: Upgraded to xenial on 2016-12-11 (0 days ago)
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1649153
Title:
upgrade from 15.10 to 16.04 broken, bricks computer
Status in apt package in Ubuntu:
New
Bug description:
I upgraded (or tried to) from 15.10 to 16.04.
After a few errors as per bug 1561467 and a few crash-report popups
which I don't know whether were related or not, I finally got the
error message:
"Could not install the upgrades
The upgrade has aborted. YOUR SYSTEM COULD BE IN AN UNUSABLE STATE. A
recovery will run now (dpkg --configure -a)"
(emphasys added).
By clicking "Close", I expedted the "recovery" to run and hopefully recover
something, but nothing happened.
Almost immediately, the upgrade window with the checklist ("download stuff",
"install stuff", ... "cleanup", "restart computer") disappeared (without
prompting me to restart the computer) and I got a message like "Upgrade
complete. The system was updated but there were errors" or something like that.
(obviously this is all unacceptable: you tell me my system could be unusable
and don't give me a clue about what the fuck happened and what I am supposed to
do?!?)
So, I tried running "dpkg --configure -a" in a terminal, but I only
got a very long series of almost identical errors regarding dependency
problems for many many packages, which ended more or less like
"Aborting, too many errors".
After a bit of googling, I tried this which I seemed to understand could
maybe fix the issue:
sudo apt-get -f install
(or "sudo apt-get install -f", can't remember now)
This seems to have worked. I could reboot (got a couple of crash reports, I
hope they won't pop up at every reboot), my system is now 16.04 and tried some
random stuff which seems to work.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.15
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.2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Dec 11 23:17:12 2016
InstallationDate: Installed on 2013-10-11 (1157 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: apt
UpgradeStatus: Upgraded to xenial on 2016-12-11 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1649153/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1561467] Re: /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure'
Got this error while upgrading from 15.10 to 16.04. Why the fuck is this marked as fixed? I understand 15.10 has reached EOL, but bugs that prevent you from upgrading seamlessly must still be fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1561467 Title: /var/lib/dpkg/info/udev.prerm called with unknown argument 'deconfigure' Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Wily: Won't Fix Status in systemd package in Debian: Fix Released Bug description: Notification during upgrade: The upgrade will continue but the '/var/cache/apt/archives/systemd_229-3ubuntu1_amd64.deb' package may not be in a working state. Please consider submitting a bug report about it. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 225-1ubuntu9.1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Thu Mar 24 11:56:03 2016 DuplicateSignature: package:systemd:225-1ubuntu9.1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]:subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2015-01-24 (424 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: MEDION H81H3-EM2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic root=UUID=5875860d-f233-4082-93b8-7ee2fcdbacc4 ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.7 SourcePackage: systemd Title: package systemd 225-1ubuntu9.1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-03-24 (0 days ago) dmi.bios.date: 06/30/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H81EM2W08.304 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81H3-EM2 dmi.board.vendor: MEDION dmi.board.version: H81EM2W08.304 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MEDION dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH81EM2W08.304:bd06/30/2014:svnMEDION:pnH81H3-EM2:pvrH81EM2W08.304:rvnMEDION:rnH81H3-EM2:rvrH81EM2W08.304:cvnMEDION:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H81H3-EM2 dmi.product.version: H81EM2W08.304 dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1561467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491612] Re: doesn't scan for available wifi networks often enough + no way to manually force a scan
> I think do frequent automatic rescan could hurt battery life, > so menu item for manual rescan would be better idea. They don't need to be *very* frequent. Yes, the menu item for manual rescan is an absolute MUST (see below though), but it also has to rescan automatically from time to time. Also note that the system knows when it's attached to power, and hence can scan more frequently in that case (assuming battery consumption really is affected). Actually, when you manually unfold the network menu, *that* should already trigger a rescan (if the fact that it is scanning was indicated by an animation/icon, which it should, then there would be no need for a specific menu item), and also automatic rescan should be more frequent when the menu is unfolded. You aren't going to keep that menu open all the time anyway. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1491612 Title: doesn't scan for available wifi networks often enough + no way to manually force a scan Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Steps to reproduce: - turn on a wifi router nearby - click on the network applet icon Expected behavior: As soon as the new network becomes available, it should become visible in the list within few seconds (and if it is a network you have already configured and set to automatically connect to, it should connect) Observed behavior: You won't see the network show up in the list, or perhaps it will, after a few minutes. Way too much time. Additionally, there should be an item in the menu such as "scan for networks now" to force scanning for available networks. But there's no such thing even. So the only workaround is to physically disable and reenable wifi on hardware, if your computer has a button for that. That will trigger re-scanning for available networks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 2 23:48:42 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (691 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 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 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-08-15 (18 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-20T16:52:59.722501 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/2 Sixty-Seven 2dfa6e3a-076f-48f9-a40c-d182c47e4178 /org/freedesktop/NetworkManager/ActiveConnection/0 43:29:1A:07:53:91 btdisconnected /org/freedesktop/NetworkManager/Devices/3 -- -- -- eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- 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/1491612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
> Nobody at Canonical suffers from this problem? LOL I don't think anybody at Canonical actually uses it, otherwise it couldn't possibly be as broken as it is. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in NetworkManager: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1594087] [NEW] Wouldn't find any wifi network after suspend/resume, restart fixed the issue
Public bug reported: I suspended (note: suspended, not hibernated) and resumed. I do this all the time and usually the computer immediately reconnects to my wifi router. This time it didn't. So I clicked on the network icon and there were no wifi networks in the list. I turned wifi off and on via Fn+F3, which usually forces a re-scan of available wifi networks. However, it would still list no network. I repeated several times with no luck. I checked my phone which was connected to the same wifi network and working. So I restarted the computer and this time it immediately connected, and also now the other available networks are listed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.3 ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10 Uname: Linux 4.2.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 19 11:13:43 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (981 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.3 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2016-01-18 (152 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'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1594087 Title: Wouldn't find any wifi network after suspend/resume, restart fixed the issue Status in network-manager package in Ubuntu: New Bug description: I suspended (note: suspended, not hibernated) and resumed. I do this all the time and usually the computer immediately reconnects to my wifi router. This time it didn't. So I clicked on the network icon and there were no wifi networks in the list. I turned wifi off and on via Fn+F3, which usually forces a re-scan of available wifi networks. However, it would still list no network. I repeated several times with no luck. I checked my phone which was connected to the same wifi network and working. So I restarted the computer and this time it immediately connected, and also now the other available networks are listed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.3 ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10 Uname: Linux 4.2.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jun 19 11:13:43 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (981 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.3 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to wily on 2016-01-18 (152 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/ubuntu/+source/network-manager/+bug/1594087/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary
> I see, so I should use the "C" locale, > as that commonly means "I don't care about the encoding". That is JUST A WORKAROUND that seems to work, but that shouldn't be needed. This is NOT the expected behavior. > I understand that grep works in another way now. Yeah, a wrong one because it has a bug. Which by the way appears to be fixed upstream. Note that grepping an ISO-8859-file (containing non-ascii characters) with an UTF-8 locale will usually *but not always* reproduce the issue, so the behavior is not even consistent or predictable. > one could say that it is more picky, but one could also consider this an improvement, NOPE NOPE NOPE > that the file warns, that the file is somehow 'non-standard' If the intent was to warn about something, the program would print a warning (and then do its job correctly). Treating the file as BINARY, when it is not, is not a sane way to "warn" about anything. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1535458 Title: [15.10 REGRESSION] Randomly wrongly detects files as binary Status in grep package in Ubuntu: Confirmed Status in grep package in Debian: Fix Released Bug description: I have a folder with a bunch of subfolder and several hundred or thousands files, most of them PHP files (obviously text). I often use grep recursively, like this: $ grep -R somepattern * Since the upgrade from 15.04 to 15.10, it often happens that a lot of text files are wrongly treated as binary. That means that, when a match is found, instead of getting the normal output which would show the file name and the matching line (with the matching substring highlighted), I get the bogus message: binary file whatever.php matches Just to be clear: in one invocation of grep -R, I get mixed output with a lot of matches shown in the expected way and quit e a few matches shown in the wrong way, even though ALL matching files are text files. This worked as expected before the upgrade from 15.04 and 15.10. This is a HUGE issue that makes it impossible to do everyday developing work. Until you fix it, please f***ing roll back grep to the previous version, because this sh** is unusable. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: grep 2.21-2 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:43:51 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: grep 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/grep/+bug/1535458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary
** Changed in: grep (Ubuntu) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1535458 Title: [15.10 REGRESSION] Randomly wrongly detects files as binary Status in grep package in Ubuntu: Confirmed Status in grep package in Debian: Fix Released Bug description: I have a folder with a bunch of subfolder and several hundred or thousands files, most of them PHP files (obviously text). I often use grep recursively, like this: $ grep -R somepattern * Since the upgrade from 15.04 to 15.10, it often happens that a lot of text files are wrongly treated as binary. That means that, when a match is found, instead of getting the normal output which would show the file name and the matching line (with the matching substring highlighted), I get the bogus message: binary file whatever.php matches Just to be clear: in one invocation of grep -R, I get mixed output with a lot of matches shown in the expected way and quit e a few matches shown in the wrong way, even though ALL matching files are text files. This worked as expected before the upgrade from 15.04 and 15.10. This is a HUGE issue that makes it impossible to do everyday developing work. Until you fix it, please f***ing roll back grep to the previous version, because this sh** is unusable. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: grep 2.21-2 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:43:51 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: grep 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/grep/+bug/1535458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary
But it definitely affects Wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1535458 Title: [15.10 REGRESSION] Randomly wrongly detects files as binary Status in grep package in Ubuntu: Fix Committed Status in grep package in Debian: Unknown Bug description: I have a folder with a bunch of subfolder and several hundred or thousands files, most of them PHP files (obviously text). I often use grep recursively, like this: $ grep -R somepattern * Since the upgrade from 15.04 to 15.10, it often happens that a lot of text files are wrongly treated as binary. That means that, when a match is found, instead of getting the normal output which would show the file name and the matching line (with the matching substring highlighted), I get the bogus message: binary file whatever.php matches Just to be clear: in one invocation of grep -R, I get mixed output with a lot of matches shown in the expected way and quit e a few matches shown in the wrong way, even though ALL matching files are text files. This worked as expected before the upgrade from 15.04 and 15.10. This is a HUGE issue that makes it impossible to do everyday developing work. Until you fix it, please f***ing roll back grep to the previous version, because this sh** is unusable. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: grep 2.21-2 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:43:51 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: grep 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/grep/+bug/1535458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary
And again, I don't think this is the same as bug 1547466 at all, as per comment https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1547466/comments/19 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1535458 Title: [15.10 REGRESSION] Randomly wrongly detects files as binary Status in grep package in Ubuntu: Fix Committed Status in grep package in Debian: Unknown Bug description: I have a folder with a bunch of subfolder and several hundred or thousands files, most of them PHP files (obviously text). I often use grep recursively, like this: $ grep -R somepattern * Since the upgrade from 15.04 to 15.10, it often happens that a lot of text files are wrongly treated as binary. That means that, when a match is found, instead of getting the normal output which would show the file name and the matching line (with the matching substring highlighted), I get the bogus message: binary file whatever.php matches Just to be clear: in one invocation of grep -R, I get mixed output with a lot of matches shown in the expected way and quit e a few matches shown in the wrong way, even though ALL matching files are text files. This worked as expected before the upgrade from 15.04 and 15.10. This is a HUGE issue that makes it impossible to do everyday developing work. Until you fix it, please f***ing roll back grep to the previous version, because this sh** is unusable. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: grep 2.21-2 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:43:51 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: grep 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/grep/+bug/1535458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary
Sorry, not sure what you mean exactly by "affecting a release". This issue appeared at some point on wily (with some update, NOT at dist-upgrade) and I wonder how it could be ignored for so long, when it was first reported AND after it turned out that it had wrongly be marked as duplicate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1535458 Title: [15.10 REGRESSION] Randomly wrongly detects files as binary Status in grep package in Ubuntu: Confirmed Bug description: I have a folder with a bunch of subfolder and several hundred or thousands files, most of them PHP files (obviously text). I often use grep recursively, like this: $ grep -R somepattern * Since the upgrade from 15.04 to 15.10, it often happens that a lot of text files are wrongly treated as binary. That means that, when a match is found, instead of getting the normal output which would show the file name and the matching line (with the matching substring highlighted), I get the bogus message: binary file whatever.php matches Just to be clear: in one invocation of grep -R, I get mixed output with a lot of matches shown in the expected way and quit e a few matches shown in the wrong way, even though ALL matching files are text files. This worked as expected before the upgrade from 15.04 and 15.10. This is a HUGE issue that makes it impossible to do everyday developing work. Until you fix it, please f***ing roll back grep to the previous version, because this sh** is unusable. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: grep 2.21-2 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:43:51 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: grep 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/grep/+bug/1535458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 958661] Re: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings
I am using 15.10 and the situation is as described in comment #12:
incoming files sent via bluetooth are systematically rejected no matter
what.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/958661
Title:
"Receive files over bluetooth" randomly stops working - plus setting
should be available under BlueTooth settings
Status in bluez package in Ubuntu:
Confirmed
Bug description:
I often send image files via bluetooth from my android phone to my
ubuntu PC.
It worked fine until yesterday, but now I systematically get "the
remote bluetooth device rejected the request".
Nothing has changed in the way I transfer files and I'm trying from
the very same phone.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-16-generic 3.0.0-16.29
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo 32650 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 25
Simple ctrls : 16
Date: Sun Mar 18 17:55:36 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.0.0-16-generic N/A
linux-backports-modules-3.0.0-16-generic N/A
linux-firmware1.60.1
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538760] Re: battery icon gone
> 1. Is there anything for indicator-power in /var/crash? In /var/crash/ there are three files: _usr_lib_gnome-user-share_gnome-user-share.1000.crash _usr_lib_gnome-user-share_gnome-user-share.1000.upload _usr_lib_gnome-user-share_gnome-user-share.1000.uploaded In the .crash there is a line that reads: indicator-power 12.10.6+15.10.20151005.1-0ubuntu1 but above and below it is nothing more that what seems to be a list of package names. > 2. What happens if you run "$ start indicator-power" ? Now I already rebooted and the indicator is there, so it would be of no use to test, I'll have to wait until the next time it happens. ** Changed in: indicator-power (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1538760 Title: battery icon gone Status in indicator-power package in Ubuntu: Confirmed Bug description: Usually the power/battery indicator works as expected. However, now I turned on my laptop while not connected to AC power, and there is no battery icon at all. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: indicator-power 12.10.6+15.10.20151005.1-0ubuntu1 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: Wed Jan 27 22:10:15 2016 InstallationDate: Installed on 2013-10-11 (838 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-power UpgradeStatus: Upgraded to wily on 2016-01-18 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1538760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538760] Re: battery icon gone
$ dbus-send --print-reply=literal --dest=com.canonical.indicator.power /com/canonical/indicator/power org.gtk.Actions.DescribeAll Error org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.indicator.power was not provided by any .service files ** Changed in: indicator-power (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1538760 Title: battery icon gone Status in indicator-power package in Ubuntu: Confirmed Bug description: Usually the power/battery indicator works as expected. However, now I turned on my laptop while not connected to AC power, and there is no battery icon at all. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: indicator-power 12.10.6+15.10.20151005.1-0ubuntu1 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: Wed Jan 27 22:10:15 2016 InstallationDate: Installed on 2013-10-11 (838 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-power UpgradeStatus: Upgraded to wily on 2016-01-18 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1538760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538760] Re: battery icon gone
Still seeing this bug. Note that this could be pretty serious if the indicator doesn't show up when the battery gets low (which seems unlikely to happen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1538760 Title: battery icon gone Status in indicator-power package in Ubuntu: Confirmed Bug description: Usually the power/battery indicator works as expected. However, now I turned on my laptop while not connected to AC power, and there is no battery icon at all. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: indicator-power 12.10.6+15.10.20151005.1-0ubuntu1 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: Wed Jan 27 22:10:15 2016 InstallationDate: Installed on 2013-10-11 (838 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-power UpgradeStatus: Upgraded to wily on 2016-01-18 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1538760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547466] Re: grep switches into binary mode while processing a text file
> This has been the case for a long time. Nope. Just a few months. > If you try to show non-UTF-8 > data in an UTF-8 locale you'll just see garbage (or other encoding > mismatches) That doesn't mean that the file should be processed as binary. Also, previous to the regression, grep would work as expected. I guess it might fail to find matches of non-ascii characters encoded in a non-utf8 encoding (though I don't see why it couldn't decode each file according to its encoding and match the contents unicode-wise), but when grepping for "foo" it would find matches for the string "foo" both in utf8-encoded files and in iso8859-encoded files. > This bug is about switching to binary mode in the 'C' locale only. Then I wonder why somebody marked the one I reported as duplicate of this one -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1547466 Title: grep switches into binary mode while processing a text file Status in grep package in Ubuntu: Fix Released Status in grep source package in Xenial: Fix Committed Status in grep source package in Yakkety: Fix Released Status in grep package in Debian: Fix Released Bug description: I noticed this staring to happen in Xenial about two days ago. When running sbuild (or now the buildd, too), the build breaks when trying to compile a generated file. I traced the problem down to grep suddenly acting weird. When not having any language set (or a non-UTF8 mode) it will start printing some lines of a source file and then suddenly end that by printing "Binary file ... matches". With the attached file, the difference can be observed (running Xenial): LANG=C grep -v xxx grant_table.h and LANG=C.UTF-8 grep -v xxx grant_table.h SRU INFORMATION === Upstream fixes: - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (but depends on previous patches and is not sufficient by itself) - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (tests+doc) Test case: Call grep on a file or a string with non-ASCII characters in the C locale: $ echo 'héll☺ ≥x' | LC_ALL=C grep . In xenial this just shows "Binary file (standard input) matches", with the fix it should show the actual input string (with some garbled output of course as the UTF-8 chars cannot be displayed in C) Regression potential: grep is being used in tons of places; during xenial we had to fix/put a "use grep -a" workaround into a lot of packages to fix the fallout from grep 2.23 which introduced this. That said, as a result of "Binary file matches" does not give any more information than the actual string match, and scripts which get along with this answer most likely just check the exit code anyway (which does not change), the risk is bearable. We will soon do a test rebuild in yakkety with gcc-6 and grep 2.25, and will sift through the results to identify new FTBFS that are due to grep 2.25. This SRU should not be released until this happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1547466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary
Removed duplicate status as per https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1547466/comments/24 ** This bug is no longer a duplicate of bug 1547466 grep switches into binary mode while processing a text file -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1535458 Title: [15.10 REGRESSION] Randomly wrongly detects files as binary Status in grep package in Ubuntu: Confirmed Bug description: I have a folder with a bunch of subfolder and several hundred or thousands files, most of them PHP files (obviously text). I often use grep recursively, like this: $ grep -R somepattern * Since the upgrade from 15.04 to 15.10, it often happens that a lot of text files are wrongly treated as binary. That means that, when a match is found, instead of getting the normal output which would show the file name and the matching line (with the matching substring highlighted), I get the bogus message: binary file whatever.php matches Just to be clear: in one invocation of grep -R, I get mixed output with a lot of matches shown in the expected way and quit e a few matches shown in the wrong way, even though ALL matching files are text files. This worked as expected before the upgrade from 15.04 and 15.10. This is a HUGE issue that makes it impossible to do everyday developing work. Until you fix it, please f***ing roll back grep to the previous version, because this sh** is unusable. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: grep 2.21-2 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:43:51 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: grep 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/grep/+bug/1535458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary
*** This bug is a duplicate of bug 1547466 *** https://bugs.launchpad.net/bugs/1547466 (btw sorry for subscribing you to the other bug by mistake) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1535458 Title: [15.10 REGRESSION] Randomly wrongly detects files as binary Status in grep package in Ubuntu: Confirmed Bug description: I have a folder with a bunch of subfolder and several hundred or thousands files, most of them PHP files (obviously text). I often use grep recursively, like this: $ grep -R somepattern * Since the upgrade from 15.04 to 15.10, it often happens that a lot of text files are wrongly treated as binary. That means that, when a match is found, instead of getting the normal output which would show the file name and the matching line (with the matching substring highlighted), I get the bogus message: binary file whatever.php matches Just to be clear: in one invocation of grep -R, I get mixed output with a lot of matches shown in the expected way and quit e a few matches shown in the wrong way, even though ALL matching files are text files. This worked as expected before the upgrade from 15.04 and 15.10. This is a HUGE issue that makes it impossible to do everyday developing work. Until you fix it, please f***ing roll back grep to the previous version, because this sh** is unusable. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: grep 2.21-2 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:43:51 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: grep 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/grep/+bug/1535458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary
*** This bug is a duplicate of bug 1547466 *** https://bugs.launchpad.net/bugs/1547466 @Brian Murray, I resubscribed you because you marked this issue as duplicate of #1547466, I asked you if you could confirm because that seems doubtful and you didn't reply, and now at 1535458 they say it only affects xenial, while this one I am observing on wily. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1535458 Title: [15.10 REGRESSION] Randomly wrongly detects files as binary Status in grep package in Ubuntu: Confirmed Bug description: I have a folder with a bunch of subfolder and several hundred or thousands files, most of them PHP files (obviously text). I often use grep recursively, like this: $ grep -R somepattern * Since the upgrade from 15.04 to 15.10, it often happens that a lot of text files are wrongly treated as binary. That means that, when a match is found, instead of getting the normal output which would show the file name and the matching line (with the matching substring highlighted), I get the bogus message: binary file whatever.php matches Just to be clear: in one invocation of grep -R, I get mixed output with a lot of matches shown in the expected way and quit e a few matches shown in the wrong way, even though ALL matching files are text files. This worked as expected before the upgrade from 15.04 and 15.10. This is a HUGE issue that makes it impossible to do everyday developing work. Until you fix it, please f***ing roll back grep to the previous version, because this sh** is unusable. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: grep 2.21-2 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:43:51 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: grep 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/grep/+bug/1535458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547466] Re: grep switches into binary mode while processing a text file
@Brian Murray, I resubscribed you because you marked this issue as duplicate of #1535458, I asked you if you could confirm because that seems doubtful and you didn't reply, and now at 1535458 they say it only affects xenial, while this one I am observing on wily. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1547466 Title: grep switches into binary mode while processing a text file Status in grep package in Ubuntu: Fix Released Status in grep source package in Xenial: In Progress Status in grep source package in Yakkety: Fix Released Status in grep package in Debian: Fix Released Bug description: I noticed this staring to happen in Xenial about two days ago. When running sbuild (or now the buildd, too), the build breaks when trying to compile a generated file. I traced the problem down to grep suddenly acting weird. When not having any language set (or a non-UTF8 mode) it will start printing some lines of a source file and then suddenly end that by printing "Binary file ... matches". With the attached file, the difference can be observed (running Xenial): LANG=C grep -v xxx grant_table.h and LANG=C.UTF-8 grep -v xxx grant_table.h SRU INFORMATION === Upstream fixes: - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (but depends on previous patches and is not sufficient by itself) - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (tests+doc) Test case: Call grep on a file or a string with non-ASCII characters in the C locale: $ echo 'héll☺ ≥x' | LC_ALL=C grep . In xenial this just shows "Binary file (standard input) matches", with the fix it should show the actual input string (with some garbled output of course as the UTF-8 chars cannot be displayed in C) Regression potential: grep is being used in tons of places; during xenial we had to fix/put a "use grep -a" workaround into a lot of packages to fix the fallout from grep 2.23 which introduced this. That said, as a result of "Binary file matches" does not give any more information than the actual string match, and scripts which get along with this answer most likely just check the exit code anyway (which does not change), the risk is bearable. We will soon do a test rebuild in yakkety with gcc-6 and grep 2.25, and will sift through the results to identify new FTBFS that are due to grep 2.25. This SRU should not be released until this happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1547466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547466] Re: grep switches into binary mode while processing a text file
Sorry, meant to post this on the other bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1547466 Title: grep switches into binary mode while processing a text file Status in grep package in Ubuntu: Fix Released Status in grep source package in Xenial: In Progress Status in grep source package in Yakkety: Fix Released Status in grep package in Debian: Fix Released Bug description: I noticed this staring to happen in Xenial about two days ago. When running sbuild (or now the buildd, too), the build breaks when trying to compile a generated file. I traced the problem down to grep suddenly acting weird. When not having any language set (or a non-UTF8 mode) it will start printing some lines of a source file and then suddenly end that by printing "Binary file ... matches". With the attached file, the difference can be observed (running Xenial): LANG=C grep -v xxx grant_table.h and LANG=C.UTF-8 grep -v xxx grant_table.h SRU INFORMATION === Upstream fixes: - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (but depends on previous patches and is not sufficient by itself) - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (tests+doc) Test case: Call grep on a file or a string with non-ASCII characters in the C locale: $ echo 'héll☺ ≥x' | LC_ALL=C grep . In xenial this just shows "Binary file (standard input) matches", with the fix it should show the actual input string (with some garbled output of course as the UTF-8 chars cannot be displayed in C) Regression potential: grep is being used in tons of places; during xenial we had to fix/put a "use grep -a" workaround into a lot of packages to fix the fallout from grep 2.23 which introduced this. That said, as a result of "Binary file matches" does not give any more information than the actual string match, and scripts which get along with this answer most likely just check the exit code anyway (which does not change), the risk is bearable. We will soon do a test rebuild in yakkety with gcc-6 and grep 2.25, and will sift through the results to identify new FTBFS that are due to grep 2.25. This SRU should not be released until this happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1547466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547466] Re: grep switches into binary mode while processing a text file
Well, I have wily and I am observing this bug all the time (starting from a few months ago), or at least I was told that what I'm observing was a duplicate of this bug. What I see is that when I grep text files, randomly (but the same files will consistently produce the same results) text files are processed like binary files, meaning that the output is Binary file .txt matches rather than the line of text with the match. Most of the times, text files that are incorrectly processed as binary are ISO-8859-whatever encoded while files that are matched like text as expected are utf8-encoded (my locale is utf8). However, I tried with two files I created from scratch, one utf-8 and the other iso-8859, and I couldn't reproduce the issue at will. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1547466 Title: grep switches into binary mode while processing a text file Status in grep package in Ubuntu: Fix Released Status in grep source package in Xenial: In Progress Status in grep source package in Yakkety: Fix Released Status in grep package in Debian: Fix Released Bug description: I noticed this staring to happen in Xenial about two days ago. When running sbuild (or now the buildd, too), the build breaks when trying to compile a generated file. I traced the problem down to grep suddenly acting weird. When not having any language set (or a non-UTF8 mode) it will start printing some lines of a source file and then suddenly end that by printing "Binary file ... matches". With the attached file, the difference can be observed (running Xenial): LANG=C grep -v xxx grant_table.h and LANG=C.UTF-8 grep -v xxx grant_table.h SRU INFORMATION === Upstream fixes: - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (but depends on previous patches and is not sufficient by itself) - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (tests+doc) Test case: Call grep on a file or a string with non-ASCII characters in the C locale: $ echo 'héll☺ ≥x' | LC_ALL=C grep . In xenial this just shows "Binary file (standard input) matches", with the fix it should show the actual input string (with some garbled output of course as the UTF-8 chars cannot be displayed in C) Regression potential: grep is being used in tons of places; during xenial we had to fix/put a "use grep -a" workaround into a lot of packages to fix the fallout from grep 2.23 which introduced this. That said, as a result of "Binary file matches" does not give any more information than the actual string match, and scripts which get along with this answer most likely just check the exit code anyway (which does not change), the risk is bearable. We will soon do a test rebuild in yakkety with gcc-6 and grep 2.25, and will sift through the results to identify new FTBFS that are due to grep 2.25. This SRU should not be released until this happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1547466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547466] Re: grep switches into binary mode while processing a text file
> Therefore my recommendation is to drop this hackery-patchery and just upgrade xenial to grep 2.25 instead. And what about wily?? Wily hasn't reached EOL (plus xenial shouldn't have been released in the first place, bricking people's computers on upgrade or leaving them with a non working mouse just to name a couple of critical regressions I've read about) and this bug is huge. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1547466 Title: grep switches into binary mode while processing a text file Status in grep package in Ubuntu: Fix Released Status in grep source package in Xenial: In Progress Status in grep source package in Yakkety: Fix Released Status in grep package in Debian: Fix Released Bug description: I noticed this staring to happen in Xenial about two days ago. When running sbuild (or now the buildd, too), the build breaks when trying to compile a generated file. I traced the problem down to grep suddenly acting weird. When not having any language set (or a non-UTF8 mode) it will start printing some lines of a source file and then suddenly end that by printing "Binary file ... matches". With the attached file, the difference can be observed (running Xenial): LANG=C grep -v xxx grant_table.h and LANG=C.UTF-8 grep -v xxx grant_table.h SRU INFORMATION === Upstream fixes: - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (but depends on previous patches and is not sufficient by itself) - http://git.savannah.gnu.org/cgit/grep.git/commit/?id=d8a366218 (tests+doc) Test case: Call grep on a file or a string with non-ASCII characters in the C locale: $ echo 'héll☺ ≥x' | LC_ALL=C grep . In xenial this just shows "Binary file (standard input) matches", with the fix it should show the actual input string (with some garbled output of course as the UTF-8 chars cannot be displayed in C) Regression potential: grep is being used in tons of places; during xenial we had to fix/put a "use grep -a" workaround into a lot of packages to fix the fallout from grep 2.23 which introduced this. That said, as a result of "Binary file matches" does not give any more information than the actual string match, and scripts which get along with this answer most likely just check the exit code anyway (which does not change), the risk is bearable. We will soon do a test rebuild in yakkety with gcc-6 and grep 2.25, and will sift through the results to identify new FTBFS that are due to grep 2.25. This SRU should not be released until this happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1547466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565541] Re: Focused window is not always brought to front
(I meant, medium - however, even high would be ridiculous) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1565541 Title: Focused window is not always brought to front Status in xorg package in Ubuntu: Confirmed Bug description: The following steps will systematically reproduce the issue. Terminal is only an example, you can do the same with any other application that can open multiple windows. - open three terminal windows - hit Ctrl+Super+D to show the Desktop. All windows disappear as expected - click on the Terminal icon in Launcher. One of the three windows is selected and brought to front as expected - click on the Terminal icon again - when presented with the three miniature windows, click on any of them except the one you previously selected Expected result: the selected terminal window should get focus AND be brought to front Observed result: the selected window is given focus but is not brought to front. Instead, another random one of the three is brought to front. The mere fact that the focused window is not the one on the top of the stack (i.e. the one most on the front) is in itself an inconsistency that should never exist and should be forbidden at the lowest conceivable level. Note that this is a HUGE SECURITY ISSUE and as such should be marked as critical. You can be typing (or sending keystrokes) into a window without even seeing it. Since one window is brought to front, you may not realise that it is not focused (though you can tell the difference if you look at it carefully enough), and hence you may for example hit several keys including Enter thinking that the selected windows is not responding, while infact your keystrokes are all processed by the invisible focused window. You may do random stuff on the invisible focused window. You could *literally* (and I'm not abusing the word "literally") wipe out your hard drive or publish your password on Facebook; or more likely, delete files or do all kind of irreversible damages to some document of yours. Note that I reported a somewhat similar issue where a random window is focused instead of the clicked one but that's a different bug (it still happens, but I don't know how to reproduce it systematicall), and another one regarding the focused window not having the title bar and borders, but that's different too and that particular one seems to be fixed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.96 Sun Nov 8 22:33:28 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 3 21:38:07 2016 DistUpgraded: 2016-01-18 11:11:01,146 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [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 (905 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2016-01-18 (76 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.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core:
[Touch-packages] [Bug 1565541] Re: Focused window is not always brought to front
But the likelihood of doing something harmful, such as deleting a file or an item of any kind, or performing any kind of irreversible action (or even reversible action but unknowingly) is far from negligible and is enough to mark the importance as CRITICAL. I can't believe you set it to high. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1565541 Title: Focused window is not always brought to front Status in xorg package in Ubuntu: Confirmed Bug description: The following steps will systematically reproduce the issue. Terminal is only an example, you can do the same with any other application that can open multiple windows. - open three terminal windows - hit Ctrl+Super+D to show the Desktop. All windows disappear as expected - click on the Terminal icon in Launcher. One of the three windows is selected and brought to front as expected - click on the Terminal icon again - when presented with the three miniature windows, click on any of them except the one you previously selected Expected result: the selected terminal window should get focus AND be brought to front Observed result: the selected window is given focus but is not brought to front. Instead, another random one of the three is brought to front. The mere fact that the focused window is not the one on the top of the stack (i.e. the one most on the front) is in itself an inconsistency that should never exist and should be forbidden at the lowest conceivable level. Note that this is a HUGE SECURITY ISSUE and as such should be marked as critical. You can be typing (or sending keystrokes) into a window without even seeing it. Since one window is brought to front, you may not realise that it is not focused (though you can tell the difference if you look at it carefully enough), and hence you may for example hit several keys including Enter thinking that the selected windows is not responding, while infact your keystrokes are all processed by the invisible focused window. You may do random stuff on the invisible focused window. You could *literally* (and I'm not abusing the word "literally") wipe out your hard drive or publish your password on Facebook; or more likely, delete files or do all kind of irreversible damages to some document of yours. Note that I reported a somewhat similar issue where a random window is focused instead of the clicked one but that's a different bug (it still happens, but I don't know how to reproduce it systematicall), and another one regarding the focused window not having the title bar and borders, but that's different too and that particular one seems to be fixed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.96 Sun Nov 8 22:33:28 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 3 21:38:07 2016 DistUpgraded: 2016-01-18 11:11:01,146 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [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 (905 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2016-01-18 (76 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.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Touch-packages] [Bug 1566437] Re: Scrolling randomly stops working
Errata: by "is that" I meant "is there", of course ** Package changed: gnome-terminal (Ubuntu) => bash (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1566437 Title: Scrolling randomly stops working Status in bash package in Ubuntu: New Bug description: Usually, scrolling in the terminal window works as expected, which is like this: - the terminal window has a scrollbar - Assuming there are more lines (of commands you have typed + their output) than fit in the window, you can scroll up and down both by dragging the scrollbar and by using the mouse wheel However, at random times, the Terminal starts behaving like this: 1 - the scrollbar's "handle" is as high as the whole scrollbar, as if the existing lines didn't exceed the height of the window, even if that is not the case 2 - you can't scroll by dragging the scrollbar (which is consistent with 1) 3 - the scrollwheel behaves like the up and down arrow keys, that is, it scans through previously typed commands in your history. I have no idea what triggers the nonsense behavior. It seems to start happening randomly. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-terminal 3.16.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 5 19:05:18 2016 InstallationDate: Installed on 2013-10-11 (906 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to wily on 2016-01-18 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1566437/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565541] [NEW] Focused window is not always brought to front
Public bug reported: The following steps will systematically reproduce the issue. Terminal is only an example, you can do the same with any other application that can open multiple windows. - open three terminal windows - hit Ctrl+Super+D to show the Desktop. All windows disappear as expected - click on the Terminal icon in Launcher. One of the three windows is selected and brought to front as expected - click on the Terminal icon again - when presented with the three miniature windows, click on any of them except the one you previously selected Expected result: the selected terminal window should get focus AND be brought to front Observed result: the selected window is given focus but is not brought to front. Instead, another random one of the three is brought to front. The mere fact that the focused window is not the one on the top of the stack (i.e. the one most on the front) is in itself an inconsistency that should never exist and should be forbidden at the lowest conceivable level. Note that this is a HUGE SECURITY ISSUE and as such should be marked as critical. You can be typing (or sending keystrokes) into a window without even seeing it. Since one window is brought to front, you may not realise that it is not focused (though you can tell the difference if you look at it carefully enough), and hence you may for example hit several keys including Enter thinking that the selected windows is not responding, while infact your keystrokes are all processed by the invisible focused window. You may do random stuff on the invisible focused window. You could *literally* (and I'm not abusing the word "literally") wipe out your hard drive or publish your password on Facebook; or more likely, delete files or do all kind of irreversible damages to some document of yours. Note that I reported a somewhat similar issue where a random window is focused instead of the clicked one but that's a different bug (it still happens, but I don't know how to reproduce it systematicall), and another one regarding the focused window not having the title bar and borders, but that's different too and that particular one seems to be fixed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.96 Sun Nov 8 22:33:28 PST 2015 GCC version: gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 3 21:38:07 2016 DistUpgraded: 2016-01-18 11:11:01,146 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [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 (905 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to wily on 2016-01-18 (76 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.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Fri Apr 1 21:24:50 2016 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.version:
[Touch-packages] [Bug 1559747] Re: [REGRESSION] Rsync fails to send modifled files
** Changed in: rsync (Ubuntu) Status: Confirmed => Invalid ** Summary changed: - [REGRESSION] Rsync fails to send modifled files + Ignore, my bad ** Description changed: - 1) I have modified a file whose path relative to the current directory - is ./protected/controllers/MessageController.php. Incidentally, I have - also modified some files in ./protected/runtime - - 2) I do: - - $ rsync -avz --no-o --no-g --exclude-from=excludelist.txt ./protected - ./themes ./css r...@example.com:/srv/www/xxx/public_html - - The content of excludelist.txt is: - runtime/* - yiic - views/static/* - css/info_video.css - - EXPECTED: - the modified file ./protected/controllers/MessageController.php should be uploaded to the server - - OBSERVED: - it isn't. - - I had done this literally thousands of times and it always worked, until - now. - - The output was: - sending incremental file list - protected/runtime/ - - sent 40,652 bytes received 1,021 bytes 7,576.91 bytes/sec - total size is 11,521,344 speedup is 276.47 - - as if only files within protected/runtime (which is in the exclude list) - were modified. - - I repeated after modifying the file again, and this time the output was: - sending incremental file list - protected/controllers/ - protected/runtime/ - - sent 40,661 bytes received 1,026 bytes 9,263.78 bytes/sec - total size is 11,521,344 speedup is 276.38 - - as if differences were detected inside the protected/controllers/ - directory but only in files that match some of the exclude patters. - Which is not the case. I mean, there are files that have been modified - which match an excluded pattern (an autogenerated - ./protected/controllers/MessageController.php~ backup file), but the - file ./protected/controllers/MessageController.php was also modified, - doesn't match any exclude pattern, and yet is not uploaded. - - This is a HUGE, critical issue. Whatever changes were made to rsync, - they need to be URGENTLY reverted until this bug is figured out and - fixed. - - ProblemType: Bug - DistroRelease: Ubuntu 15.10 - Package: rsync 3.1.1-3ubuntu0.15.10.1 - ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 - Uname: Linux 4.2.0-34-generic x86_64 - NonfreeKernelModules: nvidia - ApportVersion: 2.19.1-0ubuntu5 - Architecture: amd64 - CurrentDesktop: Unity - Date: Sun Mar 20 17:28:36 2016 - InstallationDate: Installed on 2013-10-11 (890 days ago) - InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) - SourcePackage: rsync - UpgradeStatus: Upgraded to wily on 2016-01-18 (62 days ago) + -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1559747 Title: Ignore, my bad Status in rsync package in Ubuntu: Invalid Bug description: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1559747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1559747] [NEW] [REGRESSION] Rsync fails to send modifled files
Public bug reported: 1) I have modified a file whose path relative to the current directory is ./protected/controllers/MessageController.php. Incidentally, I have also modified some files in ./protected/runtime 2) I do: $ rsync -avz --no-o --no-g --exclude-from=excludelist.txt ./protected ./themes ./css r...@example.com:/srv/www/xxx/public_html The content of excludelist.txt is: runtime/* yiic views/static/* css/info_video.css EXPECTED: the modified file ./protected/controllers/MessageController.php should be uploaded to the server OBSERVED: it isn't. I had done this literally thousands of times and it always worked, until now. The output was: sending incremental file list protected/runtime/ sent 40,652 bytes received 1,021 bytes 7,576.91 bytes/sec total size is 11,521,344 speedup is 276.47 as if only files within protected/runtime (which is in the exclude list) were modified. I repeated after modifying the file again, and this time the output was: sending incremental file list protected/controllers/ protected/runtime/ sent 40,661 bytes received 1,026 bytes 9,263.78 bytes/sec total size is 11,521,344 speedup is 276.38 as if differences were detected inside the protected/controllers/ directory but only in files that match some of the exclude patters. Which is not the case. I mean, there are files that have been modified which match an excluded pattern (an autogenerated ./protected/controllers/MessageController.php~ backup file), but the file ./protected/controllers/MessageController.php was also modified, doesn't match any exclude pattern, and yet is not uploaded. This is a HUGE, critical issue. Whatever changes were made to rsync, they need to be URGENTLY reverted until this bug is figured out and fixed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: rsync 3.1.1-3ubuntu0.15.10.1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 20 17:28:36 2016 InstallationDate: Installed on 2013-10-11 (890 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: rsync UpgradeStatus: Upgraded to wily on 2016-01-18 (62 days ago) ** Affects: rsync (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug wily ** Description changed: 1) I have modified a file whose path relative to the current directory is ./protected/controllers/MessageController.php. Incidentally, I have also modified some files in ./protected/runtime 2) I do: - $ rsync -avz --no-o --no-g --exclude-from=excludelist.txt ./protected + $ rsync -avz --no-o --no-g --exclude-from=excludelist.txt ./protected ./themes ./css r...@example.com:/srv/www/xxx/public_html The content of excludelist.txt is: - runtime/* - yiic - views/static/* - css/info_video.css + runtime/* + yiic + views/static/* + css/info_video.css - - EXPECTED: + EXPECTED: the modified file ./protected/controllers/MessageController.php should be uploaded to the server OBSERVED: it isn't. - - I had done this literally thousands of times and it always worked, until now. + I had done this literally thousands of times and it always worked, until + now. The output was: - sending incremental file list - protected/runtime/ - - sent 40,652 bytes received 1,021 bytes 7,576.91 bytes/sec - total size is 11,521,344 speedup is 276.47 + sending incremental file list + protected/runtime/ + + sent 40,652 bytes received 1,021 bytes 7,576.91 bytes/sec + total size is 11,521,344 speedup is 276.47 as if only files within protected/runtime (which is in the exclude list) were modified. + I repeated after modifying the file again, and this time the output was: + sending incremental file list + protected/controllers/ + protected/runtime/ - I repeated after modifying the file again, and this time the output was: - sending incremental file list - protected/controllers/ - protected/runtime/ - - sent 40,661 bytes received 1,026 bytes 9,263.78 bytes/sec - total size is 11,521,344 speedup is 276.38 + sent 40,661 bytes received 1,026 bytes 9,263.78 bytes/sec + total size is 11,521,344 speedup is 276.38 as if differences were detected inside the protected/controllers/ directory but only in files that match some of the exclude patters. Which is not the case. I mean, there are files that have been modified which match an excluded pattern (an autogenerated ./protected/controllers/MessageController.php~ backup file), but the file ./protected/controllers/MessageController.php was also modified, doesn't match any exclude pattern, and yet is not uploaded. - - This is a HUGE, critical issue. Whatever changes were made to rsync, they need to be URGENTLY reverted until this bug is figured out.
[Touch-packages] [Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary
*** This bug is a duplicate of bug 1547466 ***
https://bugs.launchpad.net/bugs/1547466
However,
$ LANG=C.UTF-8 grep somestring some_iso8859_file.txt# reproduces the issue
("binary file matches")
$ LANG=C grep somestring some_iso8859_file.txt# expected
(text) output
$ LANG=C.UTF-8 grep somestring some_utf8_file.txt # expected (text)
output
$ LANG=C grep somestring some_utf8_file.txt # expected
(text) output
I don't know if this is consistent with issue 1547466
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1535458
Title:
[15.10 REGRESSION] Randomly wrongly detects files as binary
Status in grep package in Ubuntu:
Confirmed
Bug description:
I have a folder with a bunch of subfolder and several hundred or
thousands files, most of them PHP files (obviously text).
I often use grep recursively, like this:
$ grep -R somepattern *
Since the upgrade from 15.04 to 15.10, it often happens that a lot of text
files are wrongly treated as binary. That means that, when a match is found,
instead of getting the normal output which would show the file name and the
matching line (with the matching substring highlighted), I get the bogus
message:
binary file whatever.php matches
Just to be clear: in one invocation of grep -R, I get mixed output
with a lot of matches shown in the expected way and quit e a few
matches shown in the wrong way, even though ALL matching files are
text files.
This worked as expected before the upgrade from 15.04 and 15.10.
This is a HUGE issue that makes it impossible to do everyday developing work.
Until you fix it, please f***ing roll back grep to the previous version,
because this sh** is unusable.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: grep 2.21-2
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:43:51 2016
InstallationDate: Installed on 2013-10-11 (829 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: grep
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/grep/+bug/1535458/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535458] Re: [15.10 REGRESSION] Randomly wrongly detects files as binary
*** This bug is a duplicate of bug 1547466 *** https://bugs.launchpad.net/bugs/1547466 Are you sure this is the same as 1547466 ?? 1547466 describes mode switching to binary in the middle of the file. What I observe is that some text files are treated as binary. I never get an output like the one described in 1547466, where you get some matches as expected and then the output gets interrupted in the middle of the file with the phrase "binary file xxx matches". I always get either the expected text-mode output for the whole file or only the "binary match" phrase. The same files always produce the same output, consistently. To me this looks a lot like https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=799956 and not much like issue 1547466. Every single file that exhibits the issue that I have examined is ISO-8859-15. I have only looked at a few randomly. And a few that don't exhibit the issue which I have looked at randomly are all UTF-8. (to look at it I use Gedit and do a Save As; the encoding the file is in is, or is supposed to be, selected by default). However, I have created an ISO-8859-15 file from scratch from Gedit and it does not reproduce the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1535458 Title: [15.10 REGRESSION] Randomly wrongly detects files as binary Status in grep package in Ubuntu: Confirmed Bug description: I have a folder with a bunch of subfolder and several hundred or thousands files, most of them PHP files (obviously text). I often use grep recursively, like this: $ grep -R somepattern * Since the upgrade from 15.04 to 15.10, it often happens that a lot of text files are wrongly treated as binary. That means that, when a match is found, instead of getting the normal output which would show the file name and the matching line (with the matching substring highlighted), I get the bogus message: binary file whatever.php matches Just to be clear: in one invocation of grep -R, I get mixed output with a lot of matches shown in the expected way and quit e a few matches shown in the wrong way, even though ALL matching files are text files. This worked as expected before the upgrade from 15.04 and 15.10. This is a HUGE issue that makes it impossible to do everyday developing work. Until you fix it, please f***ing roll back grep to the previous version, because this sh** is unusable. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: grep 2.21-2 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:43:51 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: grep 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/grep/+bug/1535458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551515] Re: My phone's bluetooth is displayed dozens of times under the network list (wifi icon)
Forgot the attachment ** Attachment added: "Screenshot from 2016-03-01 03-21-58.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1551515/+attachment/4585531/+files/Screenshot%20from%202016-03-01%2003-21-58.png -- You received this bug notification because you are a member of Ubuntu Touch seeded 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 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/ubuntu/+source/network-manager/+bug/1551515/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1551515] [NEW] My phone's bluetooth is displayed dozens of times under the network list (wifi icon)
Public bug reported: 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'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug wily ** Summary changed: - My phone's bluetooth is displayed dozens of times under the wifi/network list + My phone's bluetooth is displayed dozens of times under the network list (wifi icon) -- You received this bug notification because you are a member of Ubuntu Touch seeded 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 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
[Touch-packages] [Bug 958661] Re: "Receive files over bluetooth" randomly stops working - plus setting should be available under BlueTooth settings
WTF it's been FOUR F***ING YEARS and the problem has only got worse.
Now the workaround in comment 11 no longer works. There's NO WAY to
receive files over bluetooth. They are systematically rejected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/958661
Title:
"Receive files over bluetooth" randomly stops working - plus setting
should be available under BlueTooth settings
Status in bluez package in Ubuntu:
Confirmed
Bug description:
I often send image files via bluetooth from my android phone to my
ubuntu PC.
It worked fine until yesterday, but now I systematically get "the
remote bluetooth device rejected the request".
Nothing has changed in the way I transfer files and I'm trying from
the very same phone.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-3.0.0-16-generic 3.0.0-16.29
ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20
Uname: Linux 3.0.0-16-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: teo 32650 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfebf8000 irq 49'
Mixer name : 'Realtek ALC660-VD'
Components : 'HDA:10ec0660,1043,0011
HDA:10573055,10431316,00100700'
Controls : 25
Simple ctrls : 16
Date: Sun Mar 18 17:55:36 2012
HibernationDevice: RESUME=UUID=b1b3e5fe-38e2-44c9-9e48-4564cd9f4d66
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: ASUSTeK Computer Inc. M51Sn
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic
root=UUID=173acbf5-26a0-49e3-8d2b-f1c142582cbf ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.0.0-16-generic N/A
linux-backports-modules-3.0.0-16-generic N/A
linux-firmware1.60.1
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: Upgraded to oneiric on 2011-12-07 (101 days ago)
UserAsoundrc:
pcm.!default { type pulse }
ctl.!default { type pulse }
pcm.pulse { type pulse }
ctl.pulse { type pulse }
dmi.bios.date: 12/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 303
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51Sn
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr303:bd12/24/2007:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51Sn
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/958661/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
