Re: Bugs in built-in file explorer in Ubuntu Desktop 18.04
> I want to report two bugs in the built-in file explorer in Ubuntu > Desktop 18.04. That's still Nautilus, right? > Bug no. 2: > > The following happens for me very frequently. I've been observing that for ages on Ubuntu 16.04, I think I might even have reported it. Unbelievable it's still unfixed in 18.04. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Bug report guide issues
> If you want people to help They don't. I mean they probably do, but they don't see people reporting bugs as helping. They treat bug reports as requests for support. > I mean seriously how can such a massive bug even get in the update. It's unbelievable how little care they put into testing upgrades. It seems like they genuinely expect users to wipe out their computer and reinstall the whole operating system from scratch every time. That's not to say that if you do, you can expect it to be free of huge crippling bugs, but anyway... > I suspect you have a hell of a lot more people upset besides me. No, what makes you think that, it's just the two of us. Il giorno mer 18 set 2019 alle ore 11:58 George Hayes ha scritto: > > How about a simple click this button here to file a bug report instead of > such a complex pile of garbage. > > Where do a I file a report about a ubuntu update issue. > Example: using ubuntu 18.04 LTS just updated like I have for ages to > 18.04.3 LTS > The update for whatever reason didn't do what it normally does. > This time it deleted all the internet interfaces and removed the network > module > So even if I wanted to re-enter the internet interface info there is no > module to use it. > > I mean seriously how can such a massive bug even get in the update. > > Back to why I am contacting you. Your page > https://help.ubuntu.com/community/ReportingBugs > Is convoluted beyond belief. > If you want people to help make it simple and easy. > Right now I have 8 servers down because of whatever idiot let that bug go > through. > I suspect you have a hell of a lot more people upset besides me. > -- > Ubuntu-quality mailing list > Ubuntu-quality@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: URGENT completely crippling regression
> > How is that? Seriously, please explain it to me @C de-Avillez Ok, thank you for clarifying. Now I understand, and I think the one who was missing something was not me but you (I hope saying thi does not go against the CoC). The TL;DR version is that you confuse reporting an issue with asking for help. > Why would I help somebody that, from the start, is aggressive (as far > as I understand it) First of all, I wasn't aggressive. I simply used a swear word a few times. If you just remove all occurrences of "f***ing" in the report (which somebody already has), there's nothing aggressive about it, just a mere description of the issue (with maybe a little bit of unnecessary emphasis on the fact that it needs to be fixed urgently - unnecessary in that it's already implicitly obvious). So let's say I was being "rude". Now, it makes makes perfect sense that you wouldn't want to help me if I was being rude. What you seem to get wrong is that, when I report a bug, I'm not asking for help, I am helping. I am letting the community know that something isn't working and I'm providing as much information as I can (which, unfortunately, often happens to be very little) that might help in narrowing down the issue. (no I don't expect to be thanked for that, obviously, even if I did that without being rude. It's literally the least I can do) Investiagting, triaging and/or fixing the issue isn't about helping the particular person who reported it (in this case me). It's about making Ubuntu better - yeah of course that in turn helps the community, and eventually that includes the particular person who reported the issue, who in this case doesn't deserve it, but that's just one out of a few million potentially affected users. > So I am picky. I can understand if an OP slips and gets aggressive > once, perhaps twice. But you have a LONG story of being aggressive > from start, and keeping on it. So I allow myself to completely > disregard you *while* you keep off the CoC. Yeah I understand why you would desregard *me* (that is once I assume that you confuse my use of language you dislike with being aggressive or disrespecting people, which I never have). I still don't think that's by any means a reason for disregarding the issues I happen to report, but obviously you are free to decide where to direct your volunteering efforts by whatever criteria you like. I was curious to understand the rationale behind these particular criteria; you have explained that, I sort of get it. Seems completely irrational to me but I get it. > *You* think you can disrespect others For the record, no I don't think I can, and I don't think I have. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: URGENT completely crippling regression
I don't know why, not only "reply" doesn't reply to the list by default, but the option to reply to the list doesn't even show up in gmail. Anyway: Il giorno sab 1 giu 2019 alle ore 00:50 Teo Tei ha scritto: > > > Il giorno ven 31 mag 2019 alle ore 21:43 C de-Avillez > ha scritto: > >> I started reading the bug, and completely lost interest when I notice >> the tone used in the description. >> >> -- >> > > How is that? Seriously, please explain it to me because I don't understand > it, and it fascinates me every single time (yeah, because it's not the > first time). > > How exactly does the tone of a particular person describing an issue > affect how much you care about the issue, which obviously does not affect > only that person but potentially every single user? > > I really don't get it. I understand you can care about a particular issue > more or less based on how much it affects you, for example, or how serious > you consider it to be for users in general, or how likely you are to be > able to contribute yourself to fixing it, or simply your personal > interests and tastes. > And I also understand how you can find the tone of a user complaining > about an issue more or less appropiate, agreeable, or acceptable. > But I don't see how on earth one thing would affect the other. I try to > put myself in your position: I imagine I am reading about some > malfunctioning of some software which I'm generally interested in in some > way (because I often contribute to it, or because I'm a user myself, or for > whatever reason, otherwise I wouldn't be reading a bug report in the first > place). Now I imagine the report is written in a way I don't like (maybe I > find it offensive or something, I don't know, just guessing), let's even > say I'm getting the impression that the person writing the bug report is a > total ***hole, I hate that guy, he even *deserves* to be suffering from the > issue! However, I don't see how that would cause me to care any less about > the issue itself. Personally, if anything, it could only make me care more, > given it would demonstrate how frustrating it can be to users suffering > from it. Or not, but in the worst case, it would make no difference > whatsoever. > > I would really love to learn about your thought process, understand this > connection between how a bug report is written (specifically the "tone": > not even the quality or quantity of the information contained in it) and > how anybody should care about that bug. Again, it fascinates me. It's a > mystery. > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
URGENT completely crippling regression
Hello, Please see this bug report, this makes many basic applications in Ubuntu completely unusable: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1831280 I haven't restarted my computer yet, I don't know if the issue would disappear after a reboot, and reappear only sporadically, or not. Either way, it needs very urgent attention. It must have been introduced by some recent update (again, unless it's something that happens randomly and sporadically and by mere chance I'm hit now for the first time). -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
[Bug 1782188] [NEW] package nvidia-opencl-icd-304 (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-opencl-icd-304-update
Public bug reported: hi, I was updating Ubuntu after long time...years My laptop is more than 10 years old Best regards teo ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-opencl-icd-304 (not installed) ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27 Uname: Linux 3.13.0-68-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.29 Architecture: i386 Date: Tue Jul 17 16:33:27 2018 DuplicateSignature: package:nvidia-opencl-icd-304:(not installed):trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-opencl-icd-304-updates 304.135-0ubuntu0.14.04.1 ErrorMessage: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-opencl-icd-304-updates 304.135-0ubuntu0.14.04.1 InstallationDate: Installed on 2012-09-01 (2145 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.18 SourcePackage: nvidia-graphics-drivers-304 Title: package nvidia-opencl-icd-304 (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-opencl-icd-304-updates 304.135-0ubuntu0.14.04.1 UpgradeStatus: Upgraded to trusty on 2015-11-11 (978 days ago) ** Affects: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 package-conflict trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782188 Title: package nvidia-opencl-icd-304 (not installed) failed to install/upgrade: trying to overwrite '/etc/OpenCL/vendors/nvidia.icd', which is also in package nvidia-opencl-icd-304-updates 304.135-0ubuntu0.14.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1782188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Download link ubuntu 17.10.1
2018-01-15 18:15 GMT+01:00 teo teo <teo89...@gmail.com>: > Is it true that infamous bug 1164016 has returned in 17.10? > > https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1164016 > > 2018-01-15 18:02 GMT+01:00 Colin Law <clan...@gmail.com>: >> On 15 January 2018 at 09:39, Rob van den Berg <r...@berghelwig.nl> wrote: >>> Hello, >>> >>> I heard on phoronix that ubuntu 17.10.1 was out and free of the bios >>> bug. I can see it is available at releases.ubuntu.com >>> >>> However, on the main download page at www.ubuntu.com/desktop/1710 it >>> still says downloading 17.10 is discouraged. >> >> I think the site has been updated. Perhaps you were looking an old >> version in your browser cache, or perhaps it has just happened. >> >> Colin >> >> -- >> Ubuntu-quality mailing list >> Ubuntu-quality@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
[Bug 1729594] [NEW] package linux-image-4.10.0-38-generic 4.10.0-38.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
Public bug reported: update of kernel fails during apt update ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-38-generic 4.10.0-38.42 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic i686 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tsenger4371 F pulseaudio Date: Thu Nov 2 13:17:46 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 HibernationDevice: RESUME=UUID=9947be18-3b74-4071-9c48-e6141f4d215b InstallationDate: Installed on 2010-05-11 (2732 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) Lsusb: Bus 001 Device 004: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO 20AWA00V00 ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=dc4e6352-2043-4579-b6a1-22929b345a6b ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2 RfKill: SourcePackage: dkms Title: package linux-image-4.10.0-38-generic 4.10.0-38.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GLET67WW (2.21 ) dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvnLENOVO:bvrGLET67WW(2.21):bd02/27/2014:svnLENOVO:pn20AWA00V00:pvrThinkPadT440p:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: 20AWA00V00 dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729594 Title: package linux-image-4.10.0-38-generic 4.10.0-38.42 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1729594/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718363] [NEW] package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4
Public bug reported: update failed ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic i686 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Sep 20 09:34:07 2017 ErrorMessage: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4 HibernationDevice: RESUME=UUID=9947be18-3b74-4071-9c48-e6141f4d215b InstallationDate: Installed on 2010-05-11 (2688 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) Lsusb: Bus 001 Device 002: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO 20AWA00V00 ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=dc4e6352-2043-4579-b6a1-22929b345a6b ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2 RfKill: SourcePackage: dkms Title: package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GLET67WW (2.21 ) dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvnLENOVO:bvrGLET67WW(2.21):bd02/27/2014:svnLENOVO:pn20AWA00V00:pvrThinkPadT440p:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: 20AWA00V00 dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718363 Title: package linux-image-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1718363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717455] Re: package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4
I running this ubuntu in a VirtualBox. It seems the error started since I tried to install the correct VirtualBox GuestExtensions. But I'm not sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717455 Title: package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1717455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717455] [NEW] package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4
Public bug reported: all kernel updates failed since I updated to 17.04 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic i686 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Sep 15 09:14:42 2017 ErrorMessage: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4 HibernationDevice: RESUME=UUID=9947be18-3b74-4071-9c48-e6141f4d215b InstallationDate: Installed on 2010-05-11 (2683 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) Lsusb: Bus 001 Device 002: ID 9710:7830 MosChip Semiconductor MCS7830 10/100 Mbps Ethernet adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: LENOVO 20AWA00V00 ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=dc4e6352-2043-4579-b6a1-22929b345a6b ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2 RfKill: SourcePackage: dkms Title: package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GLET67WW (2.21 ) dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvnLENOVO:bvrGLET67WW(2.21):bd02/27/2014:svnLENOVO:pn20AWA00V00:pvrThinkPadT440p:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: 20AWA00V00 dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717455 Title: package linux-image-4.10.0-32-generic 4.10.0-32.36 failed to install/upgrade: run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1717455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Shall I include artwork in technical documentation?
Strange argument? Indeed, it is strange that someone would argue that an increase of 100% in size is negligible. Another thing would be to argue that bandwidth doesn't matter. It doesn't to you and me, but you seem to understand that it can matter to some people, right? Because you didn't say "bandwidth isn't an issue for anybody these days", you said that particular increase of "just 90kB" in bandwidth usage is negligible. Do you seriously not understand the difference between "small" and "negligible"? 5 cents is a small amount of money. If the price of a sheet of paper (*every* sheet of paper, of course) increased by 5 cents, would that be a negligible increase in price? By the way, you should probably consider writing your messages in text rather than recording videos. For one thing, watching the video may be a problem for some people because of the bandwidth usage ;) Now, I guess I will be the one who will be accused to taking the thread just one step too off-topic. 2017-05-02 2:36 GMT+02:00 Alberto Salvia Novella <es204904...@gmail.com>: > Alberto Salvia Novella: >> Images properly optimized take a negligible amount of space. This one >> took 89.3 KB. > > Teo Teo: >> >> Which is more than 50% of the whole page download. >> Negligible, huh? > > > https://youtu.be/mOajebQVoME > > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Shall I include artwork in technical documentation?
> Images properly optimized take a negligible amount of space. This one took > 89.3 KB. Which is more than 50% of the whole page download. Negligible, huh? -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Teo and his/her problems
I've been asked for more data that would actually help make Ubuntu better which is what this list is about and I'm willing to reply, so I'm confident the moderator will be intelligent enough to let this email through. >> So it makes me wonder what is wrong with Teo's setup that it seems so >> unstable? >> Perhaps we could investigate that aspect rather fight each other. I posted this bug report: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1649153 Please reply there asking me for any additional data that you think would help investigate the issue and I'll be happy to post it if I know how to. > Agree. [...] Teo seems to be the kind of person that likes to customize > and try things on his setup, Not at all, actually. Other than installing stuff with "sudo apt-get install whatever", I have hardly ever customized anything at all. I don't even usually compile and install software from source (unless it's the only option available, and even in that case, very rarely). The only times I ever tinkered with the system was when it got broken (like with this upgrade) and I had no option but to try and fix it by following some instructions I found by googling the issue (and I don't try everything that I find, I only try out what seems to be likely to work, with as little side effects as possible). I think if my mother was using Ubuntu (my mother being an example of "avarage" non-computer-savvy user) her system would be more "customized" than mine. My system is probably as "out of the box" as a system that is actually used on a daily basis, and that was installed like 4 years ago and upgraded since then without any fresh reinstall, could possibly be. > As a Quality Team, we (or you, I'm not really active here) are not a > customer support, but we need to pay attention when something gets > fantastically wrong, like this case. Finally! -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Upgrade was a disaster as usual
Now you can safely ban me, I made my point which will be ignored as usual. Don't worry, I'll get a new account for the next upgrade. 2016-12-12 14:43 GMT+01:00 teo teo <teo897...@gmail.com>: >> Many times there has been a bug, even when it affected a minority of people, >> Teo came here bullshitting this community. > > "Bullshitting"?? > > I don't remember ever lying, exagerating or speaking nonsense. The > only thing I can be accused of is using bad language, but I have never > attacked anybody while in fact *I* was repeatedly mocked and insulted. > Oh, I can also be accused of writing off-topic, to reply to the > insults and false accusations, like I am now. > >> It really doesn't matter if it's Ubuntu or political issues, the goal is >> keeping oneself in that mood. > > You are very wrong my friend. I hate being in that "mood" and I have > no goal whatsoever of keeping myself in it. My system breaking at any > random time because of a minor update, or my computer becoming a > useless pile of metal when just upgrading the OS, that is the sort of > things that put me in that mood, as well as seeing how little the "QA" > community cares about them. > > >> Since Teo is experiencing those problems continuously, and mostly when >> upgrading to alpha releases > > "alpha" releases?? Are all non-LTS considered "alpha"? Ok, that > explains a lot of things. > > Yes, I am experiencing problems continuously because Ubuntu is full of > problems, and if it is mostly when upgrading I guess it's because > upgrades are the weakest point of Ubuntu. > You should realize that the percentage of people, among those > experiencing issues, who take the time to write to this mailing list, > is ridiculously small, so for every one or two users like me who pop > here every once in a while ranting about some issue there must be > hundreds of thousands out there silently suffering from them, many of > them probably just stopping using Ubuntu. Instead of saying "here's a > troll" you should be taking note that there some serious issue to be > addressed. > > >> I'm even considering if he isn't simply paid for anti-marketing here > > LOL, you are so ridiculous. > How many end users read this list? Do you really think [that anybody > would think] that this would be a sensible place for doing any kind of > marketing or antimarketing? -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Upgrade was a disaster as usual
> Many times there has been a bug, even when it affected a minority of people, > Teo came here bullshitting this community. "Bullshitting"?? I don't remember ever lying, exagerating or speaking nonsense. The only thing I can be accused of is using bad language, but I have never attacked anybody while in fact *I* was repeatedly mocked and insulted. Oh, I can also be accused of writing off-topic, to reply to the insults and false accusations, like I am now. > It really doesn't matter if it's Ubuntu or political issues, the goal is > keeping oneself in that mood. You are very wrong my friend. I hate being in that "mood" and I have no goal whatsoever of keeping myself in it. My system breaking at any random time because of a minor update, or my computer becoming a useless pile of metal when just upgrading the OS, that is the sort of things that put me in that mood, as well as seeing how little the "QA" community cares about them. > Since Teo is experiencing those problems continuously, and mostly when > upgrading to alpha releases "alpha" releases?? Are all non-LTS considered "alpha"? Ok, that explains a lot of things. Yes, I am experiencing problems continuously because Ubuntu is full of problems, and if it is mostly when upgrading I guess it's because upgrades are the weakest point of Ubuntu. You should realize that the percentage of people, among those experiencing issues, who take the time to write to this mailing list, is ridiculously small, so for every one or two users like me who pop here every once in a while ranting about some issue there must be hundreds of thousands out there silently suffering from them, many of them probably just stopping using Ubuntu. Instead of saying "here's a troll" you should be taking note that there some serious issue to be addressed. > I'm even considering if he isn't simply paid for anti-marketing here LOL, you are so ridiculous. How many end users read this list? Do you really think [that anybody would think] that this would be a sensible place for doing any kind of marketing or antimarketing? -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Upgrade was a disaster as usual
Ah, and after that, I got a message that said "The upgrade was complete but there was some errors". The computer didn't restart. What the f**k am I supposed to do?? 2016-12-11 22:42 GMT+01:00 teo teo <teo897...@gmail.com>: > I'm SICK of upgrading every time with the fear of bricking my computer. > > Every single distribution upgrade, something goes awfully wrong and I am > left with an unusable system, which up to now I've always been able to > recover, not without pain. > > The upgrade from 15.10 to 16.04 has been no exception. > > This time, after seeing a couple of times the message described in bug > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1561467, plus a > couple or three other crash reports, I suddenly got this error: > > "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)" > > Doesn't look promising. > > It's unbelievable how carelessly the releases are released, and it's even > more unbelievable that critical bugs that leave the user with an unusable > machine go unfixed for so long (the next version has already been out there > for a while). > > F**k you, Ubuntu. > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Upgrade was a disaster as usual
I'm SICK of upgrading every time with the fear of bricking my computer. Every single distribution upgrade, something goes awfully wrong and I am left with an unusable system, which up to now I've always been able to recover, not without pain. The upgrade from 15.10 to 16.04 has been no exception. This time, after seeing a couple of times the message described in bug https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1561467, plus a couple or three other crash reports, I suddenly got this error: "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)" Doesn't look promising. It's unbelievable how carelessly the releases are released, and it's even more unbelievable that critical bugs that leave the user with an unusable machine go unfixed for so long (the next version has already been out there for a while). F**k you, Ubuntu. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Why wasn't I notified that I was put on moderation??
Errata: > And how long after I have stopped being addressed Obviously I meant "aggressive", not "addressed" 2016-06-27 13:46 GMT+02:00 teo teo <teo89...@gmail.com>: > > Yes, you were told. > > No. I was told when my first account (teo1...@gmail.com) was put on > moderation, but not when the second was (teo89...@gmail.com), unless you > are talking about a comment of yours (or somebody) saying "Teo is STILL on > the moderation queue" (emphasys added), and at that point only the first > one was. > > > You just need to look at the archive > > I can't seem to find a search engine in the archive. However I have > searched my gmail inboxes. > > > Besides, rather than casual comments within emails to the list (of which > it may even be possible I missed some when searching), I would expect to > receive a specific automatic notification, similar to the ones you receive > when you register, verify the account, etc. > > > Getting out of moderation is easy: just don't be agressive. > > Oh really? And how long after I have stopped being addressed should I > expect to be taken out of moderation? > > > 2016-06-27 1:12 GMT+02:00 C de-Avillez <hgg...@ubuntu.com>: > >> On Fri, 24 Jun 2016 21:51:36 +0200 >> teo teo <teo89...@gmail.com> wrote: >> >> > I have realised that I have been put in moderation. Nobody notified >> > me of that, let alone explained why. >> >> Yes, you were told. You just need to look at the archive to see my >> emails about it. >> >> Getting out of moderation is easy: just don't be agressive. >> >> Cheers, >> >> ..C.. >> > > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Why wasn't I notified that I was put on moderation??
> Yes, you were told. No. I was told when my first account (teo1...@gmail.com) was put on moderation, but not when the second was (teo89...@gmail.com), unless you are talking about a comment of yours (or somebody) saying "Teo is STILL on the moderation queue" (emphasys added), and at that point only the first one was. > You just need to look at the archive I can't seem to find a search engine in the archive. However I have searched my gmail inboxes. Besides, rather than casual comments within emails to the list (of which it may even be possible I missed some when searching), I would expect to receive a specific automatic notification, similar to the ones you receive when you register, verify the account, etc. > Getting out of moderation is easy: just don't be agressive. Oh really? And how long after I have stopped being addressed should I expect to be taken out of moderation? 2016-06-27 1:12 GMT+02:00 C de-Avillez <hgg...@ubuntu.com>: > On Fri, 24 Jun 2016 21:51:36 +0200 > teo teo <teo89...@gmail.com> wrote: > > > I have realised that I have been put in moderation. Nobody notified > > me of that, let alone explained why. > > Yes, you were told. You just need to look at the archive to see my > emails about it. > > Getting out of moderation is easy: just don't be agressive. > > Cheers, > > ..C.. > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Why wasn't I notified that I was put on moderation??
I have realised that I have been put in moderation. Nobody notified me of that, let alone explained why. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Please do something about #1535458
This critical regression that renders grep unusable has been introduced a few months ago and keeps being ignored https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1535458 -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Upgrading to 16.04 can render the system permanently broken
> > I found a fix for that: > (http://tinyurl.com/btfk7g) > > I don't get the joke, sorry. [a few minutes later] Oh, I get it, how funny. > Teo Teo: > > "De-releasing" 16.04 until it is decently usable should be easy, > > shouldn't it? > > Sure: > (http://tinyurl.com/hdsahpf) > > I seem to understand you're sarchastically implying that that wouldn't be easy at all? I guess you misunderstood, then. I'm not talking about magically rolling back for the unfortunate people who already upgraded, I'm talking about limiting the damages by making it not available until it's fixed. I mean, when my computer tells me that there is an upgrade available, it's because it has asked some server, right? Even if it had already stored the response, it still has to download the upgrade from somewhere. So, I don't see the difficulty... -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
Re: Upgrading to 16.04 can render the system permanently broken
This conversation is hilarious. People in a team that calls itself the "Quality Assurance" team, debating how (or whether?) to link bugs to the 100papercuts project, and in the meantime thousands of people are upgrading Ubuntu to a new release which apparently will just brick their computer because it wasn't seriously tested before being released. And that having been known for days, while the bug causing that is still being fixed (or just figured out), not only the release hasn't been withheld, but no workaround (which apparently exists) has even been posted to the bug report about the issue causing the disaster (which would be of little help but would at least be something). Excellent "quality assurance" effort. I correct myself: this *would be* hilarious, if it wasn't sad. On 27/04/16 02:18, Alberto Salvia Novella wrote: > Flocculant: >> So I assume you're going to stop addin 100papercuts to these bug reports >> now then. > > You have not gave any reason to do so. > > One Hundred Papercuts was started by Canonical itself, it has 50 active > members who renewed their membership in the past year, it is used yearly > in Google Code-In training new contributors among thousands of students, > and it is a test bed for new quality assurance processes. > > Moreover its logo inspires the Ubuntu wallpaper, the Ubuntu phone cage, > the LibreOffice launch screen, and plenty of Ubuntu social media marketing. > > So it proves to be an inspiring and useful project. And the secret > flavour for it is having been build along with the community. > > We even wrote > (https://wiki.ubuntu.com/One%20Hundred%20Papercuts/Mission) > collaboratively. And even when we have a suggested triaging process and > a goal, I consider crucial people to do the things on their style and > have space to experiment. > > When people start telling others about stopping collaborating, staying > the same old way (they have set themselves), thinks requiring to be > super perfect to be implemented (and never reaching that level), and > effectively putting all decisions on a few, that my friend causes me a > great feeling of rejection. Not because of me, but rather because of > others probably quitting contributing to the project I made my standard. > -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
[Bug 1566828] Re: Suspension does not work, freezes the pc
Ubuntu 16.04 64-bit on Dell Inspirion 7548 with Intel i7 and and Intel HD5500 + AMD Radeon R7. System not suspending just screen goes black and then you can't do anything. In previous version there wasn't this problem. One question. If i disable the "radeon module", this mean that I will use only the Intel card? Thanks a lot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566828 Title: Suspension does not work, freezes the pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: There's an idiot mass-closing old unfixed bugs
> When a report is filed against an old release and not yet fixed, but the > report hasn't been updated with comments indicating the issue is either > fixed or still existent in the future releases, I would mark as "Incomplete" > with a canned comment similar to "[...]" That sounds about right, but that's not what dino99 is doing. He is CLOSING the issues. > I am not going to look through all your bugs, but the typical triage > procedure *is* to Close or Invalid or Incomplete (or Won't Fix for > series-targeted task items) EOL-release bugs. Well, then the typical triage procedure is wrong. And there's a big difference between close/invalid/wontfix and incomplete. > Back a couple years after > Karmic went End of Life, I went through and, with the API, mass closed at > least 70 bugs still targeted to the Karmic release. You should be ashamed of yourself. > That's not the task of everyone - ideally, yes, everyone would test, but > it's not a requirement in all cases, Well, if they are not willing to test, then they shouldn't close the issue. If it's not their task to test, ask someone else whose task it is, and only after an issue is verified to be fixed or invalid, close it. > While that may not apply here, it still is valid to make note that you can > always make a comment without being rude that the issue still exists, and > ask for the bug to be reopened. I did exactly that (except perhaps the part about not being rude, but i was just responding to a rude behavior), and I myself re-open the issue, and it got closed again. Now explain how that is not stupid. > The Code of Conduct [1] states in it two big issues of which you > didn't do here: Be Considerate, Be Respectful. I am considerate and respectful to those who are considered and respectful. Closing an issue which a person took the time to report, without taking the time to verify whether it's fixed or not, is very disrespectful not only to the person who reported it, but also to everybody affected by it. > I don't see abuse here - they're not idiotic, they're just trying to clean > up old ancient bugs that are against EOL releases, and haven't yet been > marked as being affecting a later release. Well, *that* is idiotic, because by following that logic (note that it includes closing the issue WITHOUT testing whether or not it affects a later release), EVERY SINGLE BUG that is not fixed before the EOL will be closed before it's fixed. > This doesn't mean the user is an 'idiot' or being abusive. That's your > opinion because they're your bugs - that isn't a valid opinion overall. They are not "my bugs", they are every user's bugs. It's funny that the whole way you handle bugs seems to assume that the bugs somehow concern only the person who happen to report them. That also applies to the practice of closing a bug that remains "incomplete" (or "needinfo" or whatever it's called) when you ask the reporter for more information and the reporter just doesn't reply. And regarding my opinion not being valid overall, I just argued against that in my previous comment. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
There's an idiot mass-closing old unfixed bugs
Hi, I'd like to bring your attention to the harmful conduct of a user handling bugs in Launchpad. There's this "dino99", who is closing several bug reports just "because they are old", regardless of whether they are fixed or not. I think he should be stopped before he keeps doing damage. I have seen half a dozen bugs which I had reported myself ages ago, closed in the last few days by this guy. So I have re-checked some of those issues, and every single one of them still exists unfixed. I believe closing bugs without verifying them, just because they are old and haven't been acted upon, is a demential and harmful conduct. Bugs shouldn't be closed unless it is verified that they are fixed or invalid. Even worse, after I have wasted my time re-checking the issues (something he should have done before closing them in the first place) and verifying that they still exist in the current version of Ubuntu, and hence have re-opened the issues, he insists in closing them. Apparently he thinks I (or whoever reported the issue originally) should file a new identical bug report, which seems to me a ridiculous waste of time. Have a look at this: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/747197 and other issues recently closed by dino99 and/or commented by teo1978 (whcih is me). In the case of the abovementioned issue, dino99 in his last comment includes a link to some unrelated stuff which I don't know if he thinks has some relation with the issue itself (which he must not have read, because it doesn't) or with his threat to "act". It looks like he's mentally ill or something. P.S.: I suggest that you don't waste your time replying to this message because I am not going to look at the messages in this mailing list and hence am very unlikely to read any reply. -- Ubuntu-quality mailing list Ubuntu-quality@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
[Bug 1566828] Re: Suspension does not work, freezes the pc
Have the same problem on Dell Insprion 7548. Similarly, suspend worked in 15.10 but stopped in 16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566828 Title: Suspension does not work, freezes the pc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1566828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547487] [NEW] Focused window not visible
Public bug reported: The screenshot shows a situation that shouldn't ever be possible under any circumstances: The currently focused window, which should be on the foreground, is invisible. I have several applications open and I switched from one to another several times. Among them is one Nautilus window. Now, I click on the Nautilus icon in the Launcher, and the Nautilus window which gets focus does not appear anywhere. You can tell that every other window looses focus, and you can see that the Launcher icon has the triangle on the right indicating the Nautilus window has focus. Also, the menu on the top of the screen is Nautilus's. No matter how many times I try to switch window, no matter if I show and hide desktop, there's no way I get to see that window. There's NO EASY WAY TO REPRODUCE THAT I KNOW OF (hence please don't tell me "can't reproduce", I don't expect you to be able to). It just happened. I guess this is extremely rare. I seem to remember this is not the very first time I see this happen, but it might well be just the second. In my whole life. Still a bug. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.3+15.10.20151203-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Feb 19 12:59:07 2016 InstallationDate: Installed on 2013-10-11 (860 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to wily on 2016-01-18 (32 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Attachment added: "Screenshot from 2016-02-19 13-00-41.png" https://bugs.launchpad.net/bugs/1547487/+attachment/4575570/+files/Screenshot%20from%202016-02-19%2013-00-41.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547487 Title: Focused window not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1547487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1544701] [NEW] [REGRESSION] systematically unable to receive files via bluetooth
Public bug reported: I used to be able to send files over bluetooth from my smartphone to my ubuntu laptop. Then at some point bug 958661 appeared, where the undiscoverable setting for receiving files over bluetooth (which cannot be found under any bluetooth-related setting) was turned off without a reason, and also, at random times Ubuntu would start to reject all transfer despite that setting being turned on - but at least there was the workaround to manually switch the setting off and on which would "fix" the issue. Now after upgrading to 15.10 I am simply UNABLE to send any file via bluetooth from the android phone to the ubuntu laptop. ALL transfers systematically fail. On the phone side, sometimes I get "connectuion failed" and sometimes "transfer rejected on target" (I am quoting the messages by memory, so the wording may not be exact). Something as trivial and vital as transfering files over bluetooth is still broken (and gets more broken at every upgrade) after so many years. This is outrageous. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 11 20:14:51 2016 InstallationDate: Installed on 2013-10-11 (853 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to wily on 2016-01-18 (24 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 hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: A4:17:31:0D:4A:70 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:35370 acl:131 sco:0 events:112 errors:0 TX bytes:5086 acl:26 sco:0 commands:65 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1544701 Title: [REGRESSION] systematically unable to receive files via bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1544701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539938] [NEW] Show Desktop keyboard shortcut stops working after taking screenshot
Public bug reported: These steps systematically reproduce the issue: 1. make sure you have some application window on the foreground (e.g. Google Chrome) 2. hit Shift+PrintScreen to take a partial screenshot 3. Select the area for the screenshot by clicking and dragging 4. (IMPORTANT) Use the dropdown selector to choose a location other than the default for choosing the folder to save the screenshot to (if you skip this step you won't reproduce the issue) 5. hit Ok => the screenshot is saved and the Screenshot application is closed 6. Hit Ctrl+Super+D (repeat several times if you like) Expedted behavior: after step 5 focus should be returned to the application that had it before you took the screenshot. And most importantly, whether or not this happens, step 6 should show desktop Observed behavior: after step 5 the application on the foreground has lost focus, and at step 6 Ctrl+Super+D does nothing Note that even if it's the Screenshot application triggering the issue, either Xorg or Unity, or whatever piece of software is responsible for keyboard shortcuts and for showing the Desktop, MUST guarantee that (i) keyboard shortcuts always work and (ii) show desktop always work. So, no matter whether or not the Screenshot application is doing something wrong, the mere fact that a buggy (or malicious) application can prevent Show Desktop from working as expected represents a bug in the piece of software responsible of keyboard shortcuts or of the Show Desktop action (whichever of them is failing). The Screenshot application probably has a bug in that it fails to return focus to the application which had it, but again, this should not prevent the Show Desktop shortcut from working. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151016-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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Jan 30 17:19:40 2016 InstallationDate: Installed on 2013-10-11 (840 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to wily on 2016-01-18 (12 days ago) ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Also affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Show Desktop keyboard shortcut stops working + Show Desktop keyboard shortcut stops working after taking screenshot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539938 Title: Show Desktop keyboard shortcut stops working after taking screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1539938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1539964] [NEW] file information not shown on rollover on tab if window is maximized
Public bug reported: Steps to reproduce: 1. open several files in Gedit 2. maximize the window 3. move the cursor over each tab Expected behavior: every time you roll over a tab, a black rectangle should appear with white text with information about the file (full path, mime type...) Observed result: for the left-most tabs and while the cursor x position is lower than a certain point, the info box is not shown. Instead, a strange flickering can be observed on the top left corner of the screen (not even in the area where the info box is supposed to be shown); sometimes you may see the info box appear for a fraction of an instant. If you move the cursor to the right of a certain threshold and for subsequent tabs, it works as expected. Just another pathetic regression in f***ing-unusable 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 30 19:09:37 2016 InstallationDate: Installed on 2013-10-11 (841 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: Upgraded to wily on 2016-01-18 (12 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1539964 Title: file information not shown on rollover on tab if window is maximized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1539964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535465] Re: Implement and support downgrade
But that will be when, in 2020?? In the meantime, everybody who upgraded to 15.10 is fucked, because it is completely unusable due to the astonishing number of critical regressions. Either fixes for the huge number of critical regressions are released very soon, or a downgrade to 15.04 should be provided urgently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535465 Title: Implement and support downgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1535465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1538760] [NEW] battery icon gone
Public bug reported: 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) ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538760 Title: battery icon gone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1538760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1483388] Re: System randomly won't complete boot
*** This bug is a duplicate of bug 1516216 *** https://bugs.launchpad.net/bugs/1516216 Are you sure it's a duplicate? This one happened randomly, the other one is described as 100% systematic. This one results in the "Ubuntu..." screen being displayed forever, the other one results in a black screen. In my case the issue disappeared after I uninstalled/purged the nvidia drivers and (probably weeks later) reinstalled them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1483388 Title: System randomly won't complete boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1483388/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1330960] Re: [REGRESSION 14.04] keyboard configuration systematically wrong after every boot
How many decades is it going to take to triage, let alone fix, this bug? Still an issue in 15.10. I'm confirming the bug despite it's my own because I have observed it on at least two computers. ** Changed in: console-setup (Ubuntu) Status: New => Confirmed ** Description changed: I have a spanish keyboard correctly configured as a spanish keyboard. It's the only keyboard configuration I have. On the upper right corner of the screen there's an indicator that reads "Es", and if I click it, "Spanish" is the only option and it is selected. All this is as expected. This applies to both the laptop's built-in keyboard and an external usb keyboard that I always keep connected (together with an external screen) when my laptop is at home on my desktop. - SINCE THE UPGRATE TO 14.04, every time I boot, both keyboards start - behaving as if they were US english keyboards. + SINCE THE UPGRATE TO 14.04, every time I boot, both keyboards start behaving as if they were US english keyboards. + [UPDATE: I think it's not systematically every time, more like randomly half of the times] If I click on the Es indicator mentioned above, where "Spanish" already appears as selected, and I re-select it, it fixes the issue. Also, for the external keyboard, another workaround that works is to unplug and replug the keyboard. After that, the keyboard works as expected as a Spanish keyboard. - - Please don't tell me to update the bios, because this worked before on the same machine until recently. It broke with some update, most probably with the upgrade from 13.10 to 14.04. - + Please don't tell me to update the bios, because this worked before on + the same machine until recently. It broke with some update, most + probably with the upgrade from 13.10 to 14.04. P.S. I ran "ubuntu-bug keyboard-configuration", I don't know why "console-setup" got selected instead. I'm not sure what package the issue belongs to, anyway. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: keyboard-configuration 1.70ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 17 14:15:21 2014 InstallationDate: Installed on 2013-10-11 (248 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: console-setup UpgradeStatus: Upgraded to trusty on 2014-05-24 (23 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1330960 Title: [REGRESSION 14.04] keyboard configuration systematically wrong after every boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1330960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535452] Re: [15.10 REGRESSION] Builtin laptop display doesn't turn back on when external hdmi monitor is unplugged
Importance "medium"??? Do you realize the possible consequences of not being able to turn the screen on? You may suspend with a screen connected, disconnect it, take the laptop away, resume from suspend where you don't have a screen available, and you would be unable to save your work! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535452 Title: [15.10 REGRESSION] Builtin laptop display doesn't turn back on when external hdmi monitor is unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1535452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535456] Re: Xorg crashed when attempting to turn on laptop's builtin display
WTF a xorg crasher "medium"?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535456 Title: Xorg crashed when attempting to turn on laptop's builtin display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1535456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535452] [NEW] [15.10 REGRESSION] Builtin laptop display doesn't turn back on when external hdmi monitor is unplugged
Public bug reported: I used to have my display settings so that only one external monitor would be used when available, and the laptop's builtin monitor would be disabled. When plugging and unplugging the external monitor (whether in the VGA or HDMI port), monitors would switch automatically, as is obviously expected. After upgrading from 15.04 to 15.10, as per bug #1535436, these settings were lost, and after reboot, the two monitors were both enabled in extended desktop mode (or whatever it's called). So I went to Settings -> Displays (while I had an HDMI monitor connected), and turned off the builtin display. That worked, but when unplugging the HDMI monitor, the builtin one remains turned off despite being the only available monitor. No matter how many times I plug and unplug the external HDMI monitor, the builtin one never turns on (the external one does work). This is a HUGE regression as it may leave you without screen. By plugging a monitor via the VGA port, it works as expected. I'm testing with the same monitors and cables (and computer) as I was using in 15.04 when everything worked fine. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-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: Mon Jan 18 22:18:48 2016 DistUpgraded: 2016-01-18 11:11:01,146 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-43-generic, x86_64: installed bbswitch, 0.7, 4.2.0-23-generic, x86_64: installed nvidia-340, 340.96, 3.19.0-43-generic, x86_64: installed nvidia-340, 340.96, 4.2.0-23-generic, x86_64: installed vboxhost, 4.3.14: added 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 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-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 (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+15.10.20151015-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: Mon Jan 18 17:01:13 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change 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.17.2-1ubuntu9.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535452 Title: [15.10 REGRESSION] Builtin laptop display doesn't turn back on when external hdmi monitor is unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1535452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1535456] [NEW] Xorg crashed when attempting to turn on laptop's builtin display
Public bug reported: Having been hit by bug #1535452 (please see the description), I went back to Display settings and I tried to manually turn on the laptop's builtin display that I had previously turned off (obviously did this while the external monitor was connected). When I clicked on the button to turn on the builtin display, xorg crashed. Since this is a crasher, and potentially leads to disastrous data loss (imagine you are left with no monitor and can't save your work prior to switching off the laptop), I'll set this to confirm because there's no point in waiting for some other random user to confirm it. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-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: Mon Jan 18 22:33:36 2016 DistUpgraded: 2016-01-18 11:11:01,146 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-43-generic, x86_64: installed bbswitch, 0.7, 4.2.0-23-generic, x86_64: installed nvidia-340, 340.96, 3.19.0-43-generic, x86_64: installed nvidia-340, 340.96, 4.2.0-23-generic, x86_64: installed vboxhost, 4.3.14: added 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 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-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 (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+15.10.20151015-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: Mon Jan 18 17:01:13 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change 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.17.2-1ubuntu9.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug ubuntu wily ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535456 Title: Xorg crashed when attempting to turn on laptop's builtin display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1535456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535446] Re: [REGRESSION] NVidia Settings systematically crashes on "Detect displays"
Please release an update immediately reverting all the changes that were made, until this (and a bunch of other) issues are fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535446 Title: [REGRESSION] NVidia Settings systematically crashes on "Detect displays" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1535446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535446] [NEW] [REGRESSION] NVidia Settings systematically crashes on "Detect displays"
Public bug reported: Steps to reproduce: - open Nvidia Settings - go to "X Server Display Configuration" - click "Detect Displays" => systematically crashes This has started happening after upgrading from 15.04 to 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nvidia-settings 352.21-0ubuntu1 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:09:51 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nvidia-settings UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535446 Title: [REGRESSION] NVidia Settings systematically crashes on "Detect displays" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1535446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535446] Re: [REGRESSION] NVidia Settings systematically crashes on "Detect displays"
Since this is a crasher and a very critical bug that makes the whole system unusable, there's no point in waiting for some other random user to stumble upon the report and confirm it, so I'm marking it as confirmed. ** Changed in: nvidia-settings (Ubuntu) Status: New => Confirmed ** Description changed: Steps to reproduce: - open Nvidia Settings - go to "X Server Display Configuration" - click "Detect Displays" => systematically crashes + + This has started happening after upgrading from 15.04 to 15.10. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nvidia-settings 352.21-0ubuntu1 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:09:51 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nvidia-settings UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535446 Title: [REGRESSION] NVidia Settings systematically crashes on "Detect displays" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1535446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535465] [NEW] Implement and support downgrade
Public bug reported: Upgrading to 15.10 has been a catastrophe. Half an hour of use was enough to find like a dozen of critical regressions making the system unusable. Everything is broken, just look at my latest bug reports. While you keep releasing major upgrades with so little testing and such a low quality assurance, you should make downgrading easy. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.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 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Jan 18 23:06:50 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug dist-upgrade wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535465 Title: Implement and support downgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1535465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535436] [NEW] Display settings got lost in the upgrade from 15.04 to 15.10
Public bug reported: On my laptop I had my display set up this way, had been so for a very long time: - whenever I connected an external monitor, the built-in monitor would turn off and the external one would be the only enabled monitor - obviously when I disconnected the monitor, the built-in one would turn on again I think the way I had set this up in the first place was by going to Settings->Display with the external monitor connected, turning off the built-in one and leaving only the external one turned on. I don't seem to remember I had to do anything special to have it switch automatically. Which is as it should obviously be: if the built-in monitor is turned off, it must automatically turn on when it becomes the only available one (unless there was a setting whether or not to do so, which doesn't exist). Whatever the way I had set this up in the first place, the issue is that after upgrading from 15.04 to 15.10 THE SETTING GOT LOST, and both monitors were enabled in a dual-screen mode, an extended desktop or whatever it is called (where both screens are turned on and they are not cloned). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.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 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Jan 18 21:33:32 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535436 Title: Display settings got lost in the upgrade from 15.04 to 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1535436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535439] [NEW] ubuntu-bug should check for internet connection before it starts doing anything
Public bug reported: Steps to reproduce: 1. Disconnect from the internet 2. from a terminal, run "ubuntu-bug some-package" Expected result: should immediately warn me that I am not connected to the internet. Observed result: wastes my time collecting bug data and, in some cases depending on the package, prompting for the sudo password. Only after that, when it tries to connect to send the bug report, does it realize there's no internet connection and it issues an error saying so. Also note that there's no "Retry" button, which makes the issue worse. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport 2.19.1-0ubuntu5 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 21:33:57 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535439 Title: ubuntu-bug should check for internet connection before it starts doing anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1535439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535453] [NEW] [15.10 REGRESSION] Default browser setting lost, and cannot be saved
Public bug reported: On 15.04, I had Chrome set as the default browser. It had been the default browser ever since I had installed it, ages ago, several major ubuntu releases ago. After upgrading to 15.10 and rebooting, I launched Chrome and the prompt showed up telling me Chrome is not the default browser, and asking me whether to set it as the default browser. This is already an issue in itself. Even worse, I choose Yes, but the every time I restart Chrome, the same prompt shows up again. It's like not only the default browser setting was reset, but it also fails to be overwritten when I am prompted and choose Yes. P.S. I have no idea whether Unity is the right package responsible of this. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151016-0ubuntu1 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Jan 18 22:28:03 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535453 Title: [15.10 REGRESSION] Default browser setting lost, and cannot be saved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1535453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535458] [NEW] [15.10 REGRESSION] Randomly wrongly detects files as binary
Public bug reported: 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) ** Affects: grep (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535458 Title: [15.10 REGRESSION] Randomly wrongly detects files as binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1535458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535461] [NEW] [15.10 REGRESSION] Find has become sensitive to differences in accents
Public bug reported: Steps to reproduce: - write (or paste, or load) a text containing the string "marÃa" - hit Ctrl+F - in the search box, type "maria" Expected: should find the string "marÃa" in the text, because à and i only differ by an accent. This is the way it used to work, and it is the way every decent editor works Observed: doesn't find the matching string unless you type it exactly with the same accents. I already reported this upstream at https://bugzilla.gnome.org/show_bug.cgi?id=760810 However, they'll probably tell me that I'm using a too old version. - Please check whether it is already fixed in a later version upstream - if so, release the fixed version in Ubuntu - if not, either patch it or immediately roll back to the version without the issue. This makes ctrl+F unusable. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 18 22:54:37 2016 InstallationDate: Installed on 2013-10-11 (829 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gedit UpgradeStatus: Upgraded to wily on 2016-01-18 (0 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535461 Title: [15.10 REGRESSION] Find has become sensitive to differences in accents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1535461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174007] Re: release upgrader launches browser as root
WTF two f***ing years later and still not fixed. Exact same issue upgrading from 15.04 to 15.10 Also note that launching the browser as root is a huge SECURITY issue, how can the importance possibly be just "medium"?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174007 Title: release upgrader launches browser as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1174007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1535098] [NEW] Bullshit link in Release Notes window
Public bug reported: I launched the distribution upgrade for upgrading from 15.04 to 15.10. The "Release notes" popup appeared, which has a paragraph that reads: """ To see what's new in this release, visit: http://www.ubuntu.com/desktop/features """ That link is just a generic list of features of Ubuntu and doesn't contain even the slightest bit of information about "what's new in this release". Please either replace the link with a more specific release notes or changelog link, or rephrase the text introducing the link. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-release-upgrader-core 1:15.04.14.3 ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10 Uname: Linux 3.19.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Sun Jan 17 17:10:31 2016 InstallationDate: Installed on 2013-10-11 (827 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to vivid on 2015-08-15 (154 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1535098 Title: Bullshit link in Release Notes window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1535098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532017] [NEW] No option to suspend when power critically low; hibernate option greyed out
Public bug reported: (no idea whether this is the right package) In Power Settings, under "on battery" and "when power is critically low", the only available option is "Power Off". The "Hibernate" option is greyed out, and the option "Suspend" doesn't even exist, which is completely stupid. Maybe hibernation is greyed out for the same reason why it's not available in the shutdown menu, that is, because it's unreliable as hell. Besides the fact that it's about time to fix it, given we have already reached W in the alphabet of versions, anyway, since most of the time it works, the option should be available with a warning that it may fail to resume, rather than completely unavailable. Regarding the "Suspend" option, it's simply stupid that it's not available. I know, suspend requires a minimum amount of power. But the solution to that is pretty obvious: if the selected choice is to suspend, then use a slightly higher threshold for triggering suspension. And if while suspended the power goes below the lower critical threshold for keeping suspension, then it should wake up and hibernate, or turn off (there should be an additional option for this). I remember a few versions ago the option to suspend on low power did exist, and what happened was that the system started to suspend, immediately wake up, suspend again, and so on forever until the power was too low and it just hard-powered off. Now, I understand that was pathetic, but the new behavior is no solution. Also this proves that waking up when power reaches critical level while suspended is possible. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: powermgmt-base 1.31+nmu1 ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10 Uname: Linux 3.19.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 7 23:31:53 2016 Dependencies: InstallationDate: Installed on 2013-10-11 (818 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: powermgmt-base UpgradeStatus: Upgraded to vivid on 2015-08-15 (145 days ago) ** Affects: powermgmt-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: "Screenshot from 2016-01-07 23:34:13.png" https://bugs.launchpad.net/bugs/1532017/+attachment/4545898/+files/Screenshot%20from%202016-01-07%2023%3A34%3A13.png ** Description changed: (no idea whether this is the right package) In Power Settings, under "on battery" and "when power is critically low", the only available option is "Power Off". The "Hibernate" option is greyed out, and the option "Suspend" doesn't even exist, which is completely stupid. - Maybe hibernation is greyed out for the same reason why it's not available in the shutdown menu, that is, because it's unreliable as hell. + Maybe hibernation is greyed out for the same reason why it's not available in the shutdown menu, that is, because it's unreliable as hell. Besides the fact that it's about time to fix it, given we have already reached W in the alphabet of versions, anyway, since most of the time it works, the option should be available with a warning that it may fail to resume, rather than completely unavailable. Regarding the "Suspend" option, it's simply stupid that it's not available. I know, suspend requires a minimum amount of power. But the solution to that is pretty obvious: if the selected choice is to suspend, then use a slightly higher threshold for triggering suspension. And if while suspended the power goes below the lower critical threshold for keeping suspension, then it should wake up and hibernate, or turn off (there should be an additional option for this). I remember a few versions ago the option to suspend on low power did exist, and what happened was that the system started to suspend, immediately wake up, suspend again, and so on forever until the power was too low and it just hard-powered off. Now, I understand that was - pathetic, but the new behavior is no solution. + pathetic, but the new behavior is no solution. Also this proves that + waking up when power reaches critical level while suspended is possible. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: powermgmt-base 1.31+nmu1 ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10 Uname: Linux 3.19.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 7 23:31:53 2016 Dependencies: - + InstallationDate: Installed on 2013-10-11 (818 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: powermgmt-base UpgradeStatus: Upgraded to vivid on 2015-08-15 (145 days ago) -- You received this bug notification because you are a member of Ubuntu
[Bug 1526082] [NEW] Area of screenshot remains highlighted until application closed
Public bug reported: Steps to reproduce: - hit shift+PrintScreen - Drag and drop to select a rectangular area of the screen to take a screenshot of - don't close the Gnome Screenshot dialog. Minimize it if you want Observed issue: the rectangular area that has been captured remains slightly highlighted (i.e. brighter) as long as the Gnome Screenshot application's dialog is open. No matter what window is on the foreground (or even fullscreen for that matter), you'll keep noticing the slightly brighter rectangle. See attachment screenshot: you can see the rectangle approximately at the center of the screen. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-screenshot 3.14.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-37.42-generic 3.19.8-ckt9 Uname: Linux 3.19.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 14 23:20:01 2015 InstallationDate: Installed on 2013-10-11 (794 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to vivid on 2015-08-15 (121 days ago) ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: "Screenshot from 2015-12-14 23:20:30.png" https://bugs.launchpad.net/bugs/1526082/+attachment/4534777/+files/Screenshot%20from%202015-12-14%2023%3A20%3A30.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526082 Title: Area of screenshot remains highlighted until application closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1526082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415637] Re: Finding an application to launch from Dash is ridiculously slow
Sorry but (if you're talking to me) I'd rather not mess around with that as I don't fully understand the implications and possible side effects. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415637 Title: Finding an application to launch from Dash is ridiculously slow To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1415637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1523002] Re: dpkg systematically freezes the whole system, can't install anything
Changing to confirmed though it's my own issue because there's no point in waiting for another random user to stumble upon this: it not only crashes the whole system but also renders it unupdatable and prevents from installing anything, which is almost equivalent to BRICKING THE COMPUTER. Needless to say this is CRITICAL. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523002 Title: dpkg systematically freezes the whole system, can't install anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1523002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1523002] Re: dpkg systematically freezes the whole system, can't install anything
Somehow, at a third retry, all went fine without errors. However, this is still terrible and needs to be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523002 Title: dpkg systematically freezes the whole system, can't install anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1523002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1523002] [NEW] dpkg systematically freezes the whole system, can't install anything
Public bug reported: A few days ago, while installing automatic updated (in the "background" while doing other stuff, so I didn't know it was because of the updates), the whole system froze, that is, stopped responding to mouse, keyboard and anything. Not even Ctrl+Alt+F1 would work, so the only thing I could do was a hard power off. I rebooted and I thought that had been something sporadical, but now I wanted to install some package, namely yasm, so I did: $ sudo apt-get install yasm and the output was: E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. I ran 'sudo dpkg --configure -a' There were a few scary lines in the output regarding grub and linux images (as if it was reinstalling and/or reconfiguring grub for some reason), including: killed done Then after some more lines like "Processing triggers for whatever" it repeated the stuff about grub. It got stuck for several minutes after a message that read something like "Windows loader found at /what/ever" (got stuck meaning it would neither produce any more output nor would it exit to the command line), without consuming any significant amount of cpu. Some minutes later, Chrome would only display blank pages, and while I was clicking on Google Chrome's window's button to close it, the whole system stopped responding again, forcing me once more to power it down the "hardware" way. I repeated the whole process once more. So: dpkg is broken, MY WHOLE SYSTEM IS BROKEN and I can't install any packages or system updates. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dpkg 1.17.25ubuntu1.1 ProcVersionSignature: Ubuntu 3.19.0-37.42-generic 3.19.8-ckt9 Uname: Linux 3.19.0-37-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 5 01:07:08 2015 InstallationDate: Installed on 2013-10-11 (784 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: dpkg UpgradeStatus: Upgraded to vivid on 2015-08-15 (111 days ago) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523002 Title: dpkg systematically freezes the whole system, can't install anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1523002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1523002] Re: dpkg systematically freezes the whole system, can't install anything
Changing to confirmed as per http://ubuntuforums.org/archive/index.php/t-1269182.html (two-thousand-f***ing-nine!) ** Changed in: dpkg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523002 Title: dpkg systematically freezes the whole system, can't install anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1523002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519099] Re: no icons on ubuntu 15.10. ; program freezes often "clip couldn't be updated"
Great info, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519099 Title: no icons on ubuntu 15.10. ; program freezes often "clip couldn't be updated" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdenlive/+bug/1519099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1400840] Re: package libasound2 1.0.27.2-1ubuntu6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instance
delete the file by doing a find -name then reinstall. On 07/06/2015 11:30 pm, Edel edelcustodiofr...@gmail.com wrote: Someone have fixed this kind of error? I have a few weeks with this problem and I'm losing my head, please help me. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1400840 Title: package libasound2 1.0.27.2-1ubuntu6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances of package libasound2:amd64 Status in alsa-lib package in Ubuntu: New Bug description: does not seem to be able to install properly as similar package exist of a different signature. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libasound2 1.0.27.2-1ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 AptOrdering: libasound2: Install libasound2: Configure libasound2: Configure Architecture: amd64 Date: Wed Dec 10 03:46:06 2014 Dependencies: gcc-4.9-base 4.9-20140406-0ubuntu1 libasound2-data 1.0.27.2-3ubuntu7 libc6 2.19-0ubuntu6.3 libgcc1 1:4.9-20140406-0ubuntu1 multiarch-support 2.19-0ubuntu6 DpkgHistoryLog: Start-Date: 2014-12-10 03:45:20 Commandline: aptdaemon role='role-fix-broken-depends' sender=':1.87' Upgrade: libasound2:amd64 (1.0.27.2-1ubuntu6, 1.0.27.2-3ubuntu7) DpkgTerminalLog: Preparing to unpack .../libasound2_1.0.27.2-3ubuntu7_amd64.deb ... Unpacking libasound2:amd64 (1.0.27.2-3ubuntu7) over (1.0.27.2-1ubuntu6) ... dpkg: error processing archive /var/cache/apt/archives/libasound2_1.0.27.2-3ubuntu7_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances of package libasound2:amd64 DuplicateSignature: package:libasound2:1.0.27.2-1ubuntu6:trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances of package libasound2:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances of package libasound2:amd64 InstallationDate: Installed on 2013-08-31 (465 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: alsa-lib Title: package libasound2 1.0.27.2-1ubuntu6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances of package libasound2:amd64 UpgradeStatus: Upgraded to trusty on 2014-07-30 (131 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1400840/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400840 Title: package libasound2 1.0.27.2-1ubuntu6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances of package libasound2:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1400840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446738] [NEW] 3.5mm audio jack output not working (on Nexus10-UT 15.04 r2)
Public bug reported: On Nexus 10 with UT 15.04 r2 audio output by 3.5 audio jack don't work. Instead speakers work properly and sound is very good. ** Affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Tags: 3.5mm headphones nexus10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446738 Title: 3.5mm audio jack output not working (on Nexus10-UT 15.04 r2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1446738/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445954] [NEW] Sorting of folders by modification date is meaningless
Public bug reported: Steps to reproduce - open a folder that contains subfolders (and optionally files), of which at least some contains in turn at least a couple of levels of subfolders with files inside it - select list view - click on the modified column to sort items by modification date Expected: * both the files and folders should be ordered by modification date. For folders, modification date should be the date of last modification of the item most recently modified inside the folder, RECURSIVELY. That is, for example, the folder containing the file most recently modified, at ANY level of its subtree, should be considered the most recently modified folder Observed: * Files stright inside the current folder are ordered correctly, but folders are ordered in a seemingly random manner. Often, the folder that you'd expect to be on the top of the list (in reverse chronological order) is pretty close, but many times it's not, and the overall sorting certainly doesn't satisfy the expected criteria. I suspect the modification dates of items inside the folders are taken into account but not recursively. If that is the case, it's a meaningless and hence wrong criteria. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.7 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 19 18:22:28 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2013-10-11 (554 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-05-24 (329 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445954 Title: Sorting of folders by modification date is meaningless To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1445954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1444568] [NEW] [REGRESSION] shutdown from menu does nothing until you press the hardware button
Public bug reported: I'm not sure this is systematic. Lately, this happens to me very often, but I'm not sure it's 100% of the times. If not, it's pretty close. Steps to reproduce: 1. Click on the gear icon on the top right corner of the screen 2. From the dropdown menu, select shut down 3. From the popup dialog (whether to shutdown or restart) choose Shut Down Expected: = system should shut down (well, actually it should first bring up dialogs for each program with unsaved data asking whether to save, but it's stopped to do that long ago and that's a separate regression) Observed: = NOTHING happens Now: 4. Repeat steps 1 and 2 Expected: = the popup should appear asking whether to shutdown or restard Observed: = nothing happens 5. Press the hardware power button (a short press is enough). = NOW it will shut down. Which is the workaround This is a regression. Not sure when it started but perhaps a few weeks or months ago. ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: I'm not sure this is systematic. Lately, this happens to me very often, but I'm not sure it's 100% of the times. If not, it's pretty close. Steps to reproduce: 1. Click on the gear icon on the top right corner of the screen 2. From the dropdown menu, select shut down 3. From the popup dialog (whether to shutdown or restart) choose Shut Down Expected: = system should shut down (well, actually it should first bring up dialogs for each program with unsaved data asking whether to save, but it's stopped to do that long ago and that's a separate regression) Observed: = NOTHING happens Now: 4. Repeat steps 1 and 2 Expected: = the popup should appear asking whether to shutdown or restard Observed: = nothing happens 5. Press the hardware power button (a short press is enough). = NOW it will shut down. Which is the workaround + + + This is a regression. Not sure when it started but perhaps a few weeks or months ago. ** Summary changed: - shutdown from menu does nothing until you press the hardware button + [REGRESSION] shutdown from menu does nothing until you press the hardware button -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1444568 Title: [REGRESSION] shutdown from menu does nothing until you press the hardware button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1444568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 907411] Re: printer tray icon doesn't appear (any more) when printing
The bug is still present in 14.04. @3 instead of just marking it as invalid you could have changed the package to the correct one. This way perhaps it wouldn't have gone unfixed for two years ** Also affects: indicator-printers Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/907411 Title: printer tray icon doesn't appear (any more) when printing To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-printers/+bug/907411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1417568] Re: diff reports bogus differences on identical files
I forgot to change the incomplete status when I responded to the request for information. ** Changed in: diffutils (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1417568 Title: diff reports bogus differences on identical files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/diffutils/+bug/1417568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318363] Re: can't download this youtube video
On trusty:
$ youtube-dl https://www.youtube.com/watch?v=t0On9tbnKd8
[youtube] Setting language
[youtube] t0On9tbnKd8: Downloading webpage
[youtube] t0On9tbnKd8: Downloading video info webpage
[youtube] t0On9tbnKd8: Extracting video information
[youtube] t0On9tbnKd8: Encrypted signatures detected.
WARNING: Automatic signature extraction failed: Traceback (most recent call
last):
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
957, in _decrypt_signature
video_id, player_url, len(s)
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
331, in _extract_signature_function
player_type = id_m.group('ext')
AttributeError: 'NoneType' object has no attribute 'group'
WARNING: Warning: Falling back to static signature algorithm
WARNING: Automatic signature extraction failed: Traceback (most recent call
last):
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
957, in _decrypt_signature
video_id, player_url, len(s)
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
331, in _extract_signature_function
player_type = id_m.group('ext')
AttributeError: 'NoneType' object has no attribute 'group'
WARNING: Warning: Falling back to static signature algorithm
WARNING: Automatic signature extraction failed: Traceback (most recent call
last):
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
957, in _decrypt_signature
video_id, player_url, len(s)
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
331, in _extract_signature_function
player_type = id_m.group('ext')
AttributeError: 'NoneType' object has no attribute 'group'
WARNING: Warning: Falling back to static signature algorithm
WARNING: Automatic signature extraction failed: Traceback (most recent call
last):
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
957, in _decrypt_signature
video_id, player_url, len(s)
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
331, in _extract_signature_function
player_type = id_m.group('ext')
AttributeError: 'NoneType' object has no attribute 'group'
WARNING: Warning: Falling back to static signature algorithm
WARNING: Automatic signature extraction failed: Traceback (most recent call
last):
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
957, in _decrypt_signature
video_id, player_url, len(s)
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
331, in _extract_signature_function
player_type = id_m.group('ext')
AttributeError: 'NoneType' object has no attribute 'group'
WARNING: Warning: Falling back to static signature algorithm
WARNING: Automatic signature extraction failed: Traceback (most recent call
last):
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
957, in _decrypt_signature
video_id, player_url, len(s)
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
331, in _extract_signature_function
player_type = id_m.group('ext')
AttributeError: 'NoneType' object has no attribute 'group'
WARNING: Warning: Falling back to static signature algorithm
WARNING: Automatic signature extraction failed: Traceback (most recent call
last):
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
957, in _decrypt_signature
video_id, player_url, len(s)
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
331, in _extract_signature_function
player_type = id_m.group('ext')
AttributeError: 'NoneType' object has no attribute 'group'
WARNING: Warning: Falling back to static signature algorithm
WARNING: Automatic signature extraction failed: Traceback (most recent call
last):
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
957, in _decrypt_signature
video_id, player_url, len(s)
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
331, in _extract_signature_function
player_type = id_m.group('ext')
AttributeError: 'NoneType' object has no attribute 'group'
WARNING: Warning: Falling back to static signature algorithm
WARNING: Automatic signature extraction failed: Traceback (most recent call
last):
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
957, in _decrypt_signature
video_id, player_url, len(s)
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
331, in _extract_signature_function
player_type = id_m.group('ext')
AttributeError: 'NoneType' object has no attribute 'group'
WARNING: Warning: Falling back to static signature algorithm
WARNING: Automatic signature extraction failed: Traceback (most recent call
last):
File /usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py, line
957, in _decrypt_signature
video_id, player_url, len(s)
File
[Bug 1318363] Re: can't download this youtube video
@2: $ sudo youtube-dl -U [sudo] password for teo: It looks like you installed youtube-dl with a package manager, pip, setup.py or a tarball. Please use that to update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318363 Title: can't download this youtube video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/youtube-dl/+bug/1318363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268257] Re: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file
I like the official Nvidia drivers better regardless because they are built specifically for and by Nvidia for Nvidia products Except they don't support Optimus boards on Linux, so they are just not an option for those of us who have one. https://www.youtube.com/watch?v=iYWzMvlj2RQ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268257 Title: nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1268257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
So, I'm getting tired of always unchecking Grub from automatic updates just to be sure that my system won't break again at the next reboot, and I would also like to upgrade to Ubuntu 14.10, which I have been delaying so far for the same reason (and then, 15.04 must be almost out). As a remainder: I was one of the people whose working dual boot system was screwed up when upgrading from 13.10 to 14.04 (because of a misconfigured system according to Phillip Susi, which I doubt, but if it is the case, it was misconfigured because of some bug in the first place) So, is this what I need to do in order to prevent my computer from being bricked again by an upgrade? dpkg-reconfigure grub-pc Will this ensure that updating grub and upgrading to 14.10 won't screw things up again? And then I guess that will ask me for some parameters, or to choose something. If so, what command should I run to figure out what my current perfectly working configuration of grub is and make sure it is preserved, and/or to figure out the correct answer to whatever dpkg- reconfigure prompts may show up? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
FIRST Hence, if you are not willing to help debug this at all, how would you expect any developers to want to work on your issue? It is not my issue, it's everybody's issue. I just happen to be somebody who experienced and reported it. I don't expect anything from any developer if by expect we mean think they should or have to. But if by expect we mean merely to regard as probable or likely; anticipate, then given that there are developers who work in improving and fixing Ubuntu, whatever is the reason that moves them to devote their effort to make Ubuntu a better software (something I appreciate and for which I'm infinitely grateful), I do expect them to be interested in fixing a bug regardless of whether the person who reported it is able (or willing) to do any extra work. Because whether or not I do, the bug is there. That's what I would do if somebody reported to me a bug in some piece of software I had written (or which I happened to be maintaining) SECOND by not testing the upstream kernel, you are limiting the developers who are going to look at this to only downstream (Ubuntu) developers. Your are ASSUMING that this is a bug in Linux. I reported it against linux just because I didn't know a way to report it generically (and the ubuntu-bug command doesn't seem to provide a way), but it's not clear at all what package the bug belongs to, so even BEFORE we talk about upstream/downstream, this should be triaged. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
By the way: by not testing the upstream kernel, you are limiting the developers who are going to look at this to only downstream (Ubuntu) developers. And by marking it as incomplete and let it expire, you are limiting the developers who are going to look at this to nobody. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430578] [NEW] Drag'n'drop a file onto a zip file gives nonsense error message
Public bug reported: Steps to reproduce: - pick or create a zip file (e.g. select some files and compress them) - drag another file and drop it over the zip file Expected: should add the dragged file to the contents of the compressed file. Observed: shows a popup with this error message that doesn't even make sense: An error occurred while adding files to the archive. You can't add an archive to itself ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.6 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 23:28:08 2015 GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2013-10-11 (515 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-05-24 (290 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430578 Title: Drag'n'drop a file onto a zip file gives nonsense error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1430578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
I'm not upgrading the BIOS (nonsense requirement) and I'm not testing the mainstream kernel (no time to do that). That should not be a reason for closing the bug. I have reported it and it's as much as I can do. This might not even be in the kernel, I reported it against linux just because I have no idea what package is really responsible. That the OP (in this case me) isn't willing to do additional debugging work doesn't mean the bug should expire, it's not like the person who reports it is the only one affected. ** Changed in: linux (Ubuntu) Status: Expired = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1216869] Re: package libasound2 1.0.27.2-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances of
can't seem to do as described hence it is a confirmed bug... joey@joey-i7qm:~$ sudo apt-get install --reinstall libasound2:amd64 [sudo] password for joey: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libc6-i386 libssl0.9.8 Use 'apt-get autoremove' to remove them. The following packages will be upgraded: libasound2 1 upgraded, 0 newly installed, 0 to remove and 493 not upgraded. 2 not fully installed or removed. Need to get 0 B/327 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 334940 files and directories currently installed.) Preparing to unpack .../libasound2_1.0.27.2-3ubuntu7_amd64.deb ... Unpacking libasound2:amd64 (1.0.27.2-3ubuntu7) over (1.0.27.2-1ubuntu6) ... dpkg: error processing archive /var/cache/apt/archives/libasound2_1.0.27.2-3ubuntu7_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances of package libasound2:amd64 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libasound2_1.0.27.2-3ubuntu7_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1216869 Title: package libasound2 1.0.27.2-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances of package libasound2:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1216869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1400840] [NEW] package libasound2 1.0.27.2-1ubuntu6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances
Public bug reported: does not seem to be able to install properly as similar package exist of a different signature. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libasound2 1.0.27.2-1ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 AptOrdering: libasound2: Install libasound2: Configure libasound2: Configure Architecture: amd64 Date: Wed Dec 10 03:46:06 2014 Dependencies: gcc-4.9-base 4.9-20140406-0ubuntu1 libasound2-data 1.0.27.2-3ubuntu7 libc6 2.19-0ubuntu6.3 libgcc1 1:4.9-20140406-0ubuntu1 multiarch-support 2.19-0ubuntu6 DpkgHistoryLog: Start-Date: 2014-12-10 03:45:20 Commandline: aptdaemon role='role-fix-broken-depends' sender=':1.87' Upgrade: libasound2:amd64 (1.0.27.2-1ubuntu6, 1.0.27.2-3ubuntu7) DpkgTerminalLog: Preparing to unpack .../libasound2_1.0.27.2-3ubuntu7_amd64.deb ... Unpacking libasound2:amd64 (1.0.27.2-3ubuntu7) over (1.0.27.2-1ubuntu6) ... dpkg: error processing archive /var/cache/apt/archives/libasound2_1.0.27.2-3ubuntu7_amd64.deb (--unpack): trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances of package libasound2:amd64 DuplicateSignature: package:libasound2:1.0.27.2-1ubuntu6:trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances of package libasound2:amd64 ErrorMessage: trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances of package libasound2:amd64 InstallationDate: Installed on 2013-08-31 (465 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: alsa-lib Title: package libasound2 1.0.27.2-1ubuntu6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances of package libasound2:amd64 UpgradeStatus: Upgraded to trusty on 2014-07-30 (131 days ago) ** Affects: alsa-lib (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1400840 Title: package libasound2 1.0.27.2-1ubuntu6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libasound2/changelog.Debian.gz', which is different from other instances of package libasound2:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1400840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1390892] [NEW] Windows stacking (foreground/background) gets completely screwed up
Public bug reported: I have reported several issues (none of which got the slightest attention, by the way) but I now realize they ALWAYS happen all together, so they are most surely just consequences of one same issue. At random times it happens that the front/back or in-front/behind relation between windows becomes badly screwed up in several ways: 1 - windows are on top of Launcher while Launcher should always be the topmost 1b - even the context menu of Launcher icons that appear by right-clicking on them turns out to be behind maximized windows (or non maximized windows) 2 - the window-switching selector that shows up when you hit Alt+Tab is on the background (hence invisible most of the time unless you minimize all windows or show desktop) 3 - Fullscreen content from any browser, such as for example fullscreen of video or flash content, goes fullscreen on the background instead of on the foreground; even clicking on it (if some portion of it is visible behind the foremost windows) doesn't bring to the foreground, the only workaround (which was difficult to figure out) being: ctrl+super+d and then click on the browser launcher icon. Sometimes (3) is slightly different, in that the fullscreen content stays on top of everything except Launcher. All of this is very annoying and this issue has been around for a very long time, certainly more than a year (i.e. two releases) if not forever. This cripples the usability of the whole system to the point that one is forced to restart, which is painful. This should be high priority. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Nov 9 12:46:03 2014 InstallationDate: Installed on 2013-10-11 (393 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (168 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1390892 Title: Windows stacking (foreground/background) gets completely screwed up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1390892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
Then your 14.10 install did not install grub correctly ( i.e. it failed to install, or installed it to a place your system did not actually boot from ), leaving the previous grub install you had to try and fail to boot. Which confirms there's a bug somewhere. The bottom line is that this message happens because you have one version of grub in your MBR, and a different version in your /boot directory. Which is something that should never happen no matter what. The very fact that this can happen is _the_ bug (unless, of course, one manually runs a command to purposefully create that situation, with some kind of --force option or after answering yes to a warning prompt). Assuming that your diagnosis is correct, that is. Of which I am not completely sure, given that you have a history of negating facts (as in I haven't seen anyone report this on a fresh install). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
No, it does not. Installing grub to the wrong place because you manually chose it is not a bug. Who talked about manually choosing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
Never happen no matter what is asking for a magic wand and unicorns. No matter what was a sloppy phrasing, agreed. I should have said whenever it can be avoided. No need for magic wand or unicorns, just a few checks. And here it definitlely can be avoided at least to some extend, while absolutely nothing is done to even attempt to avoid that. There are some things we can control, and some we can not. And here, there are definitely things that can, and hence should, be controlled, and that are not being controlled, hence a bug. Note that I'm always talking about Ubuntu as a whole; which part of it is responsible for doing right what is being done wrong, I don't know. It may be Grub, it may be the Grub packaging in Ubuntu, or it may be some other part of ubuntu. Ubuntu is miserably failing to provide an easy or at least reliable way to install it in dual-boot on a system that has another OS, namely Windows 8. Following the instructions that are given during installations fails. Following the instructions that are given in the official docs fails. You're left alone either tinkering or using third party repair tools. And when you do and get it to work, a system upgrade on a machine that works breaks it. That's simply not an acceptable UX. That's my experience. Other users have reported doing a bare fresh zero-tinkering install immediately resulting in a broken system, or doing a bare fresh zero-tinkering install which resulted in a working system which broke at some later dist-upgrade. That's something that should never happen, and here I really can say no matter what. Comments 55, 91, 137 report cases where absolutely no manual installation or third party tools were ever used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
If you fixed it correctly so the package system knows where it needs to reinstall it in the future, then you won't have the problem again. If you fixed it by manually reinstalling grub outside the package system again, then you will face the problem again. I'm not sure how I fixed it. I followed the instructions provided in some of the comments above by some other victim of the issue. But it was almost certainly the second way. Will I (and others in my situation) hit the problem again only when dist-upgrading to 14.10 (which is already out btw) or also when installing the grub updates that have been available for a while? (which I have always avoided installing just in case)? Secondly and most important, what should I do so that the package system knows whatever it needs to know, so that I can dist-upgrade without screwing up my working system again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
@psusi No, as already discussed, there is a broken installation of grub. The reason Colin reopened this report is because he wants to put in some checks at some point to detect that it's broken and guide you through fixing it. You start with No,, but you confirm what I said. Note I didn't say the bug is in grub itself; I have no idea whether it's in grub or in Ubuntu or in Ubuntu's packaging of grub, but something is broken if this situation happens in the first place. there is a broken installation of grub If there is a broken installation, something is broken. A few users got that broken installation after a fresh install, so some piece of software responsible for installing it didn't do its job correctly. I (and others) got that broken installation after having to manually touch things because the Ubuntu installer just hadn't been capable of installing the system. I didn't tinker with things because I wanted to, I was forced to because the Ubuntu installer doesn't do its job and the docs don't offer any instructions that work, so I had to try things. If I happened to touch something wrong, it was because I was forced to touch things that I shouldn't even have had to touch. Colin reopened this report is because he wants to put in some checks at some point to detect that it's broken and guide you through fixing it. Which is what must be done to fix this issue. A robust OS (like any robust piece of software) cheks things and warns you if it's going to break. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
I haven't seen anyone report this on a fresh install. It is always after an upgrade, That's untrue and you know it. There are a few comments on this very page reporting the issue on fresh install. And you did see them; I seem to remember you said you just don't believe them (I'm too lazy to look for it now), but that's a different thing. Anyway, as already discussed, there is clearly some bug, whether it is in Grub or in Ubuntu, if a perfectly working dual boot (whether it was a fresh install or it was tinkered because that is the _only_ way to get a dual boot with windows 8 to run, as the official installer and all the officially documented methods fail to produce a working dual boot installation) gets bricked by a distupgrade without warning. The maintainer of the Ubuntu package himself agreed to that. By the way, talking about @cjwatson, I'm still wating for an answer to whether or not those of us who were bitten by the bug and and fixed the broken boot can safely install the updates that have since been released, and whether the upgrade to 14.10 will bite us again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385264] [NEW] wrong media type association for wav files
Public bug reported: Steps to reproduce: - In Nautilus or in the Desktop, double click on a .wav file Expected: - should open in the dafault audio player (Rhythmbox or whatever it is called) Observed: - it opens in the default video player (Totem) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 24 14:56:17 2014 InstallationDate: Installed on 2013-10-11 (377 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: meta-gnome3 UpgradeStatus: Upgraded to trusty on 2014-05-24 (152 days ago) ** Affects: meta-gnome3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385264 Title: wrong media type association for wav files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1385264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380320] Re: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad
For god's sake, the impact of this is huge. Because of this bugs I have moved messages in Thunderbird from a random folder to another, which is equivalent to loosing them (impossible to figure out what I moved where), moved entire folders; the same with files in Nautilus. I have devastated Android Studio projects. All because a mouse press even is registered at a random point in space and time (it actually follows a strict logic as described in the report, but that is unrelated with the real behavior of the hand on the touchpad). This is like having a cat walking on your keyboard. Well, actually it's worse; the probability of doing serious damages is higher. This needs urgen attention. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380320 Title: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1380320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380320] Re: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad
Oh, I forgot, among the disasters that happened to me because of this bug, I also accidentally sent emails that I hadn't finished writing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380320 Title: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1380320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380320] Re: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad
There seems to be also another (dangerous and annoying) glitch of which I can't find the exact pattern. Often I click with the touchpad button and TWO consecutive clicks are registered (not necessarily a double click). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380320 Title: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1380320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380320] [NEW] [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad
Public bug reported: This is a REGRESSION. This used to work fine. I don't know when exactly it broke. Steps to reproduce: Test 1 and Test 2 should both behave the same as test 2, but test 1 gives nonsense and dangerous results. --Test 1-- - place finger 1 on the touchpad - move the finger around while keeping it in contact with the touchpad = the mouse cursor moves around as expected - with another finger 2, press the left button and hold it, while finger 1 is still on the touchpad, at point A - (*) move finger 1 around on the touchpad to some other point B, then stop moving it - move finger 1 around again, to point C - only then, release the left button -- Test 2 -- - place finger 1 on the touchpad - move the finger around as in test 1 - take finger 1 away from the touchpad, leaving the cursor at point A - with another finger 2, press the left button and hold it - place finger 1 on the touchpad again and move it around, then stop at point B. - Move finger 1 a bit more, to point C - release the left button Expected result: OBVIOUSLY, in both cases, the behavior should be the same. A left button press should be registered at point A, then a drag movement to B and then C, and then a button release. If, for example, at point A you hit something draggable, the result is that you drag it and drop to point C Observed result: Test 2 behaves as expected However, in test 1, nothing happens when you actually press the button. Instead, a button press is registered when finger 1 pauses at point B. That is, everything behaves as if you had pressed the mouse button at a completely different place and time than you did. The result is dragging from point B to point C. The consequences can be disastrous. This can lead to data loss, because a click may be registered on a button that delete things, or the drag- and-move operation that is executed (completely unrelated to the real action of the user) may be that of moving an object to a place where you're not supposed to move it (e.g. moving a file to the trash or whatever). This can literally result in formatting your hard drive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Oct 12 17:17:03 2014 InstallationDate: Installed on 2013-10-11 (365 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (140 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Summary changed: - [REGRESSION] touchpad behavior broken: left button click not caught if finger is on touchpad + [REGRESSION] touchpad behavior broken: left button click delayed if finger is on touchpad ** Summary changed: - [REGRESSION] touchpad behavior broken: left button click delayed if finger is on touchpad + [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1380320 Title: [REGRESSION] touchpad behavior broken: left button press delayed if finger is on touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1380320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301083] Re: Drag and Drop File Auto Opens Folders
How can this even be importance low? Doesn't anybody realize the huge SECURITY RISK this bug involves? You drag a file onto a folder, for just a fraction of a second more than the time it takes for the folder to auto-open. Then you drop it, but when you do, the folder has just opened and you have accidentally dropped the file onto a subfolder within the folder. Unless you double check, you may not realize where you have moved the file and you may loose it forever. You may have moved it (without realizing) into a subfolder that you will later delete, without knowing it contains a file that you never intended to move into it. This is DISASTROUS. We already know that Nautilus development has degenerated into complete dementia, and that until it gets repleced with something else in Ubuntu, it constantly needs patching to revert regressions like this one (which are made on purpose, because of demential design). But an issue like this should be considered high importance, if not critical, as it can lead to DATA LOSS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301083 Title: Drag and Drop File Auto Opens Folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1301083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
I did not add a *random* package. I added the most generic one that I could think of, as this is probably not in the linux package, and the linux package is the one that has this stupid policy of not taking bug into consideration unless they are reported on the latest bios. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
It's no surprise that Ubuntu is still what it is as long as bug reports get managed this way. This issue is intermittent, happens randomly, and is a regression (i.e. has started happening at a certain update, never happened before). Ignoring it just because the reporter doesn't have the latest bios is ridiculous. This is most probably not even in Linux; I chose linux just because I have no idea what package it belongs to, and there's no generic ubuntu package to report bugs against. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1353129] Re: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working
It's no surprise that Ubuntu is still what it is as long as bug reports get managed this ridiculous way. This issue is intermittent, happens randomly, and is a regression (i.e. has started happening at a certain update, never happened before). Ignoring it just because the reporter doesn't have the latest bios is ridiculous. This is most probably not even in Linux; I chose linux just because I have no idea what package it belongs to, and there's no generic ubuntu package to report bugs against. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1353129 Title: [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1378046] [NEW] Can't switch between maximized windows of the same program sometimes
Public bug reported: Note: this is intermittent and I don't know of a way to systematically reproduce this, but I've observed it dozens of times. - I have two windows of the same program both maximized - I click on the program's icon on the Launcher (one icon with two tips indicating there are two windows open) = the downscaled previews of the two windows are shown one on top of the other as expected - I click on one of them Expected result: the one I clicked should get focus and be brought to front (maximized, as it was) Observed result: whichever I pick, only one of them, systematically always the same one, will get chosen. That is, if I click on window A, it's window A, if I click on window B, it's window A allthesame. Additionally, the title bar on the top of the screen is not displayed. I can click on the foreground window (which is not the expected one) and interact with it. If I click on the top of the screen, where the window title is not shown, then the correct window will be brought to front (not sure this _always_ work, but I have observed it sometimes). One thing that fixes the issue is to de-maximize both windows and then remaximize them. I've only observed this on maximized windows. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Oct 6 20:00:03 2014 InstallationDate: Installed on 2013-10-11 (360 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-24 (135 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Summary changed: - Can't switch between maximized windows at random times + Can't switch between maximized windows of the same program sometimes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1378046 Title: Can't switch between maximized windows of the same program sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1378046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284308] Re: Bogus another operation in progress error. Can't copy files from a bluetooth device
As usual, importance (after months undecided) gets wrongly assigned https://wiki.ubuntu.com/Bugs/Bug%20importances If those criteria are not up to date, please update that page. Otherwise try to respect them. This issue meets two of the criteria of High: - Has a severe impact on a small portion of Ubuntu users (estimated) [not being able to copy file among common devices is definitely severe impact] - Renders essential features or functionality of the application or dependencies broken or ineffective [copying files is an essential feature] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284308 Title: Bogus another operation in progress error. Can't copy files from a bluetooth device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371942] Re: this requires installation of untrusted packages: incomplete warning, then OK button does nothing
Additionally, the Settings button leads to a Tab in Settings where there's nothing related to trusted/untrusted packages. Ther relevant tab is Authentication, but you have no clue of what you are supposed to do there, because - the error message didn't tell anything about what are the problematic untrusted sources that allegedly are required - there's no option to allow untrusted sources or anything like that, so you should magically know which source you would need to add And most important, Update Manager should at the very least let you install ALL OTHER updates except the ones that are causing the issue, so at least one would be able to isolate them. Altogether this is designed in the worst conceivable way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371942 Title: this requires installation of untrusted packages: incomplete warning, then OK button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1371942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371942] Re: this requires installation of untrusted packages: incomplete warning, then OK button does nothing
The only way out is to check only one update (of the several-dozens list), install it, and then again with the next one, until you find the one that is causing the wrning. Or a few at a time, or half of them in a bisection-search-like fashion. Totally ridiculous. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371942 Title: this requires installation of untrusted packages: incomplete warning, then OK button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1371942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372077] [NEW] checking/unchecking a bunch of updates is tremendously slow and blocks the UI
Public bug reported: When you click on an item in the list of updates to check or uncheck it, it takes a riduculously long time to update the checkbox. If you check or uncheck a whole group (e.g. Security Updates or Other Updates), it takes so long that the UI stops responding and greys out for a while. There are two issue: - this shouldn't take so long in the first place - nothing that take significant time should ever, ever, block the UI, so it should be done in a separate thread so as to keep the UI always 100% responsive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: update-manager 1:0.196.12 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Sep 21 13:18:20 2014 GsettingsChanges: b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'748' b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'window-width' b'677' b'com.ubuntu.update-manager' b'launch-time' b'1411288799' InstallationDate: Installed on 2013-10-11 (344 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: Upgraded to trusty on 2014-05-24 (119 days ago) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372077 Title: checking/unchecking a bunch of updates is tremendously slow and blocks the UI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1372077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
@cjwatson again, could you please tell us whether or not it is safe to install the latest grub updates for those of us who had the bug, had the boot broken, and had fixed it? The problem is: there are updates available and I have no idea whether installing them will cause the same thing to run which screwed up the boot on dist upgrade. I appreciate comments made by other users but they don't calrify this point. I understand you cannot guarantee whether anything bad will happen or not by updating grup, but given it's you who maintains the package, you should easily know whether or not: 1 - merely installing the updates will run the same scripts that ran on distupgrade which screwed up some boot configurations 2 - the issue has been addressed in any way so that even if (1) is the case, it may not cause the disaster any more Obviously I won't take the risk if (2) is true, but I'd rather keep grub up to date if (1) is false. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371942] Re: this requires installation of untrusted packages: incomplete warning, then OK button does nothing
I meant confirmed ** Changed in: update-manager (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371942 Title: this requires installation of untrusted packages: incomplete warning, then OK button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1371942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371942] Re: this requires installation of untrusted packages: incomplete warning, then OK button does nothing
And finally, by bisection, I identified the package which was causing the warning: tortoisehg (or some of its dependencies). I had installed this package with sudo apt-get install tortoisehg. So now I ran sudo apt-get install tortoisehg from a command line and I got this prompt: WARNING: The following packages cannot be authenticated! tortoisehg mercurial mercurial-common Install these packages without verification? [y/N] Why on earth doesn't Update Manager just give the same prompt and the same Yes/No option? That's the issue. I'll change this to Verified because I think the source of the issue is pretty clear and it's nonsense to wait for some other random person to stumble into the problem, wnich is easily reproducible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371942 Title: this requires installation of untrusted packages: incomplete warning, then OK button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1371942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1371942] [NEW] this requires installation of untrusted packages: incomplete warning, then OK button does nothing
Public bug reported: I run UpdateManager, I click on Install updates and I get this error message (see screenshot): This requires installing packages from unauthenticated sources I'm SICK of Update Manager's vague error messages that don't provide the most basic information. WHAT requires installing WHICH packages from WHICH unauthenticated sources, and WHY? Also, I'm presented with a Settings button and an OK button. To me OK means Ok, proceed, I'm happy with it, do the install. Not. Turns out it means Ok, so forget about it, do nothing. The button should be disambiguated. Actually there should be two options (besides Settings): - proceed at your own risk - cancel (or abort, or whatever) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: update-manager 1:0.196.12 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 20 18:09:24 2014 GsettingsChanges: b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'748' b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'window-width' b'677' b'com.ubuntu.update-manager' b'launch-time' b'1411206597' InstallationDate: Installed on 2013-10-11 (343 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: Upgraded to trusty on 2014-05-24 (118 days ago) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1371942 Title: this requires installation of untrusted packages: incomplete warning, then OK button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1371942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
