[Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
I have encountered this issue trying a fresh install of Kubuntu 20.04.1. The entire reason that I tried a fresh install is that trying to upgrade my existing system from Ubuntu Mate 18.04 to 20.04 resulted in the upgrade finishing with errors and leaving my system in an unusable state (fortunately, I have a full backup, so rolling back a failed upgrade is painless, other than the time consumed). I don't know if the root cause of both issues is the same or not. My graphics card is an NVidia GeForce GTX 750 Ti. /var/log/syslog from the failed ground-up installation is attached (I attempted installing twice in the live session with failures both times). I will attempt to find time to retry the upgrade and attach the syslog from that so we can see if the root cause is the same (I have already rolled the filesystem back from backup for the previous attempts, so I don't have a syslog for them). The end result is that I have no upgrade path from 18.04 to 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
** Attachment added: "The attachment for my comment above does not seem to have taken. This is /var/log/syslog for a failed ground-up Kubuntu 20.04 installation" https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1871268/+attachment/5417422/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897339] [NEW] Documentation missing for "ip tuntap"
Public bug reported: Ubuntu 18.04.5 iproute2 4.15.0-2ubuntu1.2 iproute2-doc 4.15.0-2ubuntu1.2 Most of the subcommands for /sbin/ip are documented in a manpage with a name of the form "ip-$SUBCOMMAND(8)", for example "ip address" is documented at "ip-address(8)". However, ip tuntap seems to be completely undocumented, other than the one-line description given in ip(8): "tuntap - manage TUN/TAP devices." No manpage is pulled in with the iproute2 package, as with the other ip manpages, nor with the iproute2-doc package. This also seems to be the case with "ip mrule". Expected behavior: Some package can be installed that contains a manpage covering "ip tuntap". Actual behavior: No manpage for "ip tuntap" exists in either the package that contains the /sbin/ip binary, nor the corresponding -doc package. ** Affects: iproute2 (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/1897339 Title: Documentation missing for "ip tuntap" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1897339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511875] Re: Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container
As an update to my comment above, while the release upgrader hung and did not finish the upgrade, it *did* disable all my ppa's and switch over to the Xenial repositories, which ended up leaving my system broken next time I tried pulling in updates (thinking the upgrade had failed completely and the system was still using Trusty repositories). I'm not sure what packages are at Xenial versions and what packages are at still at Trusty versions, there seems to be a mix. So it seems I can't expect Ubuntu to upgrade between LTS versions without barfing all over itself. Gee, what fun. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511875 Title: Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1511875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1511875] Re: Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container
I'm running into the same thing trying to upgrade from 14.04 to 16.04. After Googling around about the issue, this link at first looked like a promising lead, as I'm running into this on Haswell hardware and I have Core2 hardware that was unaffected: https://groups.google.com/forum/#!topic/mechanical-sympathy/QbmpZxp6C64 So I tried using a custom-compiled 4.4 series kernel to see if that resolved the issue, and it does cause the upgrade to stop hanging in the futex wait channel, but, unfortunately, does not cause the upgrade to stop hanging. On the 4.4 kernel, system monitor shows the process to be in waiting channel 0 instead of the futex wait channel, but gdb shows the process to be hung in "sem_wait()". I am running into this on bare hardware, not a container or VM. Given that I'm seeing it on a Haswell machine but my Core2 laptop did not experience the hang, and given that using a newer kernel version changed the specifics of how the hang is occuring, it seems to be related to the kernel bug discussed at the Google Groups link above, but the kernel bug can't be the whole story, or else the new kernel would have fixed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511875 Title: Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1511875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965510] Re: option --new-window not working correctly
Is there any chance of this being fixed in Precise? Looking at https://wiki.ubuntu.com/StableReleaseUpdates#When , it's not really a severe regression (2nd bullet point), but I believe it qualifies for Obviously safe patch and Affects an application (4th bullet point). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965510 Title: option --new-window not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/965510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 410548] Re: when i boot in to win me It thinks I have a virus in mbr
I've recently run into this problem. From my own experience, and looking around on the net, the cause seems to be that something in the handling of chainloading or drive mapping has changed since grub-legacy, and Windows 95/98/ME thinks that it was booted from the MBR of a drive with grub on it instead of its own MBR (thus the false-positive bootsector virus detection and the use of compatibility mode). If the machine was booted with grub-legacy, or if BIOS is set to bypass grub2 and boot directly from the Windows' drive, Windows detects its own MBR and boots normally. Grub2 isn't doing anything with the MBR(s) that grub-legacy didn't do. What it *is* doing, however, is setting the machine up in such a way that Windows checks the wrong disk when doing the MBR check, sees the Grub MBR, and thinks the MBR has been modified. In short, there seems to be a regression between map in grub-legacy and drivemap in grub2 (or perhaps between chainload in grub-legacy and grub2) that causes Win95/98/ME to check the MBR on the wrong drive when booted from Grub2, but not when booted from grub-legacy or straight from BIOS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/410548 Title: when i boot in to win me It thinks I have a virus in mbr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/410548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919736] [NEW] Mounting a loop device causes the wrong loop device to be mounted.
Public bug reported: Ubuntu 10.04.3 LTS util-linux 2.17.2-0ubuntu1.10.04.2 There may be other packages involved in this bug than util-linux: This bug has only affected me for a few days, whereas Synaptic reports the last update to util-linux / mount to have been about a year ago (January 20th 2011). After setting up a loop device with losetup, mounting that loop device will cause the next available loop device to be mounted instead of the designated loop device. If the loop devices are listed in fstab, this will trigger bug 726283 when an unprivileged user attempts to unmount them. For example, with an fstab containing the following lines: /dev/loop0 /mnt/loop0 autoloop,user,noauto0 0 /dev/loop1 /mnt/loop1 autoloop,user,noauto0 0 /dev/loop2 /mnt/loop2 autoloop,user,noauto0 0 /dev/loop3 /mnt/loop3 autoloop,user,noauto0 0 /dev/loop4 /mnt/loop4 autoloop,user,noauto0 0 /dev/loop5 /mnt/loop5 autoloop,user,noauto0 0 And the following commands given: losetup /dev/loop0 image0.img losetup /dev/loop1 image1.img mount /dev/loop0 mount /dev/loop1 The following lines will be produced in /etc/mtab: /dev/loop2 /mnt/loop0 iso9660 rw,noexec,nosuid,nodev,user=username 0 0 /dev/loop3 /mnt/loop1 iso9660 rw,noexec,nosuid,nodev,user=username 0 0 And losetup -f will produce the following: /dev/loop4 Attempting to umount /dev/loop0 or /dev/loop1 will produce: umount: /dev/loop[loop device number we attempted to umount] is not mounted (according to mtab) And attempting to umount /dev/loop2 or /dev/loop3 as an unprivileged user will trigger bug 726283, as /etc/fstab and /etc/mtab are inconsistent with each other as to which loop devices are associated with which directories. In short: Expected result: The commands given above should result in the following mtab lines and losetup -f output: mtab: /dev/loop0 /mnt/loop0 iso9660 rw,noexec,nosuid,nodev,user=username 0 0 /dev/loop1 /mnt/loop1 iso9660 rw,noexec,nosuid,nodev,user=username 0 0 losetup -f: /dev/loop2 Actual result: The commands given above result in the following mtab lines and losetup -f output: mtab: /dev/loop2 /mnt/loop0 iso9660 rw,noexec,nosuid,nodev,user=username 0 0 /dev/loop3 /mnt/loop1 iso9660 rw,noexec,nosuid,nodev,user=username 0 0 losetup -f: /dev/loop4 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: mount 2.17.2-0ubuntu1.10.04.2 ProcVersionSignature: Ubuntu 2.6.32-38.83-generic 2.6.32.52+drm33.21 Uname: Linux 2.6.32-38-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Jan 21 10:40:28 2012 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: util-linux ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919736 Title: Mounting a loop device causes the wrong loop device to be mounted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/919736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919736] Re: Mounting a loop device causes the wrong loop device to be mounted.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919736 Title: Mounting a loop device causes the wrong loop device to be mounted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/919736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 726283] Re: umount segfaults with inconsistent entry in /etc/fstab
I can reproduce this bug in Lucid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/726283 Title: umount segfaults with inconsistent entry in /etc/fstab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/726283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 919736] Re: Mounting a loop device causes the wrong loop device to be mounted.
Oops. Just realized that the problem was do to the inclusion of loop,user,noauto rather than user,noauto in my fstab entries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/919736 Title: Mounting a loop device causes the wrong loop device to be mounted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/919736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913029] Re: su segfaults when Ctrl-D is entered as the first charachter in response to the password prompt
OK, yeah, I recently installed a fingerprint reader package (from this PPA: https://launchpad.net/~fingerprint/+archive/fingerprint-gui) , and I recall that a PAM module was involved. And /var/log/syslog records a segfault in a *.so associated with that package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913029 Title: su segfaults when Ctrl-D is entered as the first charachter in response to the password prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/913029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913029] [NEW] su segfaults when Ctrl-D is entered as the first charachter in response to the password prompt
Public bug reported: 64 bit Ubuntu 10.04.3 LTS login version 1:4.1.4.2-1ubuntu2.2 Steps to reproduce: 1. Invoke su. (What options and username are given, if any, doesn't seem to matter). 2. When prompted for a password, hit Ctrl-D without typing any other characters first. Expected results: su should handle Ctrl-D however it was designed to handle it without segfaulting. I had accidentally invoked su and subconsciously expected su to treat Ctrl-D as end of input and terminate (as cat or a shell would). Actual results: su terminates with a segfault. - I am not sure whether to check the This bug is a security vulnerability box. I will leave it unchecked as I'm uncertain what the criteria are for classifying a bug as a security vulnerability and as I have not observed this bug to allow a privileged login without a password, but it seems that a segfault in a program that deals with passwords, especially while handling passwords, is at least a potential vulnerability. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: login 1:4.1.4.2-1ubuntu2.2 ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32.41+drm33.18-jwb x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Jan 6 23:49:12 2012 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: shadow ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913029 Title: su segfaults when Ctrl-D is entered as the first charachter in response to the password prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/913029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913029] Re: su segfaults when Ctrl-D is entered as the first charachter in response to the password prompt
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913029 Title: su segfaults when Ctrl-D is entered as the first charachter in response to the password prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/913029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 882274] Re: Community engagement is broken
@ Tal Liron In their rush to hate on Unity, people are forgetting how keyboard-centric Unity is. Not me. For me, the fact that that keyboard centrism comes at the cost of huge regressions in mouse-centric usability is what kills it for me (that and some configurability issues, but many of those come from GNOME 3 and weren't in the GNOME 2 based Unity in 11.04, and thus aren't Canonical's fault). I'm used to being able to switch windows (or minimize a window) with a single click to a screen-edge target (the edges of the screen are the fastest to access because you don't have to worry about overshooting with the mouse. You can thus slam the mouse in the general direction of the screen edge to get it there as quickly as possible). Window management is the most common task I perform on my desktop, so it's important that I be able to do it quickly. Having multiple windows of the same program be smashed into one icon on the launcher means that accessing any window that's not the only window running for its program requires an extra click (this may be mitigated if the window isn't minimized or covered by another, but it's still not a screen-edge target in that case). It's made worse by the fact that the size of the launcher icons along the screen edge is a good deal smaller than taskbar buttons were (which makes them a smaller target that I have to aim more carefully to hit, which slows me down). Then there's the fact that the launcher's merging of quick-launch and window management functionality interferes greatly with its functionality as a launcher: Linus famously complained about similar problems in GNOME Shell: When he had a terminal open and clicked on the icon he'd used to launch it, his original terminal window got brought into focus, rather than a new one being launched. But it doesn't just apply to the terminal: It can apply to Nautilus, or gcalctool, or gedit, or OpenOffice. (Come to think of it, this goes straight against Mark's assertion that clicking twice on an icon should generally do one thing twice). Even with an option in a context menu that allows opening another copy of the program associated with the icon, it's still two clicks instead of one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882274 Title: Community engagement is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/882274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 882274] Re: Community engagement is broken
@Mark Shuttleworth: Nonsense, again. Ubuntu has *always* aimed for usability, always gone the extra mile to make it easy to install and easy to embrace and easy to share Linux. I don't think it's cool to be too cool for that mission, but if you are in fact too cool for that mission, please don't denigrate the work of those of us who care about it. It's not a matter of being too cool for the mission of making Ubuntu more usable. You've got two types of people complaining about Unity. Neither is too cool to support said mission. One group has a workstyle for which GNOME 2 is more usable than Unity and feels abandoned by the disappearance of GNOME 2 (and the fact that GNOME 3's fallback mode is a less suitable replacement than XFCE), and some members of that group don't realize that it's GNOME, not Canonical, that's responsible for there not being a suitably back-compatible replacement for GNOME 2. I belong to this group (namely, the part of it that recognizes that the disappearance of GNOME 2 is not Canonical's fault). I generally agree with them about the usability of Unity (given that a good part of the OS industry seems to be going to similar interfaces, a good chunk of the population probably has a work style for which Unity is usable. For me, however, it's totally unusable). I do, however, realize that 1) Canonical is pursuing a user base that may have an easier time with Unity, and 2) it's probably more productive to complain to the GNOME project, given that it seems much more reasonable to me for a distribution to switch DE's if it doesn't think its current DE's interaction model is the best for its target users (given that users can always go back to the previous DE) than for a DE to suddenly switch interaction models (given that a DE's core users are the users that find its interaction model to be the best in the world, and that if a DE switches models, its original model ceases to be available). This first group is making a lot of complaints that I think have been wearing your (and the rest of the Canonical team's) nerves thin, with unfortunate consequences for the second group. The second group, I think, is the one you really need to listen to. This is made up of people (like Tal Liron) that like Unity's interaction model, but find it lacking in some small way or other (as opposed to the big ways that I and others in the first group find it lacking). The important thing about this group is that it is likely to be at least somewhat representative of the new users you're aiming to acquire (assuming that the analysis that new users are more likely to be attracted by Unity is accurate). If you want to solve bug #1, you're going to have to listen to this group, especially insofar as Microsoft has implemented the features they're asking for. The second group is complaining about the fixed launcher (From screenshots I've seen, the Windows 7 task bar remains movable, as does the OS X dock) and the minimization issue (Windows has been training 90% of your potential users for years that the place you click to maximize a minimized window can also be clicked to minimize it when it's maximized, and while I haven't used Win7 a lot, I don't think it's changed anything). When you receive a complaint about Unity, ask yourself which group it's coming from. If it's coming from the first group, ignore it. We're just feeling abandoned (and not really by you) and don't know where to go next, and that makes people grumpy. If it's coming from the second group, or from both groups, take it *very* seriously, and ignore it at your peril, as it could very well be an issue that new users will have when switching. @Art Cancro: Canonical (and Mark S. in particular) are openly hostile towards the vast majority of Ubuntu users who have a strong dislike for Unity and want it removed, or at least made optional. It *is* optional. One can install XFCE and forget that Unity even exists. Many of us are now, or will soon be, ex-Ubuntu users. Why? When Lucid hits end-of-life, I will almost certainly continue using Ubuntu. I will almost certainly *not*, however, start using Unity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/882274 Title: Community engagement is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/882274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843333] [NEW] Rhythmbox delivers a misleading error message on encountering a corrupted ogg.
Public bug reported: In my ~/Music folder I have a corrupted copy of http://en.wikipedia.org/wiki/File:I.S.Bach-BWV578.ogg Naturally, Rhythmbox will often stop playing this file when in reaches the corrupt data (though exactly where it stops and if it stops is inconsistent). The problem is that twice it has given the following message after choking on the file: Search for suitable plugin? The required software to play this file is not installed. You need to install suitable plugins to play media files. Do you want to search for a plugin that supports the selected file? The search will also include software which is not officially supported. This occurs on Ubuntu 10.04.3 LTS with Rhythmbox 0.12.8-0ubuntu7 Expected results: Upon encountering corrupt data, Rhythmbox should display an appropriate error message indicating that the file type is supported by the installed plugins but the file seems to be corrupt and needs to be redownloaded. Actual results: Either no error message is displayed and playback stops (acceptable but suboptimal, and happens most of the time), or playback stops and a misleading error message is displayed indicating that a new plugin is required to read the file (this has happened twice), despite the fact that the file has already been read successfully up to the point where it is corrupted (which presumably involves determining that the file type is supported by the current plugins). ** Affects: rhythmbox (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/84 Title: Rhythmbox delivers a misleading error message on encountering a corrupted ogg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/84/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843333] Re: Rhythmbox delivers a misleading error message on encountering a corrupted ogg.
** Attachment added: The corrupted file. https://bugs.launchpad.net/bugs/84/+attachment/2364026/+files/I.S.Bach-BWV578.ogg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/84 Title: Rhythmbox delivers a misleading error message on encountering a corrupted ogg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/84/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75151] Re: Refuses to open files where the character encoding is not recognised
The thing is, this probably isn't actually a bug, but rather a misfeature, and the it's not a bug, it's a feature mentality is probably responsible for the fact that it has gone unfixed so long. I see no evidence that the behavior gedit exhibits here wasn't intended. If it *were* a bug, it would be a lot more excusable, and probably would have been fixed upstream by now. (It's been around for over *six years*. The bug report for it on the GNOME site dates back to '04). I can easily see what the misfeature in question was intended for: Protect the noobs from trashing their binaries by editing them in gedit. But at the same time, it renders any text file that has been misprocessed by an other program in such a way as to insert control characters unreadable in gedit. *Every other* text editor I've used, whether generally superior to gedit, or generally inferior to it (e.g. Notepad) operates on the garbage-in - garbage-out principal when it comes to opening binary files. This is the natural behavior of a text editor, and *not* operating on the GIGO principle requires extra effort. Furthermore, violating the GIGO principle in the fashion that gedit does ends up doing more harm than good. Gedit is otherwise a solid text editor, but this problem, whether we call it a bug or a misfeature, is a horrible annoyance that has not been fixed in almost six years, and really needs to be fixed yesterday. Unless upstream will be making a release that fixes it within a concrete and *short* time period (no more than a few months), it needs to be fixed downstream ASAP (rather than after another 6 years of thumb- twiddling). Even the current behavior would be acceptable if there were just a Open the file anyways button. Even a --force-open command line switch would be better than nothing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/75151 Title: Refuses to open files where the character encoding is not recognised -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
