[Bug 1322890] Re: CRITICAL: 13.10-14.04 upgrade BREAKS GRUP, renders computer UNBOOTABLE
*** This bug is a duplicate of bug 1289977 *** https://bugs.launchpad.net/bugs/1289977 Changing to confirmed because one single case is enough. No point in waiting for some other user to have its system destroyed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322890 Title: CRITICAL: 13.10-14.04 upgrade BREAKS GRUP, renders computer UNBOOTABLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1322890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322890] [NEW] CRITICAL: 13.10-14.04 upgrade BREAKS GRUP, renders computer UNBOOTABLE
*** This bug is a duplicate of bug 1289977 *** https://bugs.launchpad.net/bugs/1289977 Public bug reported: Great! I decided to finally upgrade from 13.10 to 14.04, and after the whole upgrade process and the restart, the computer won't boot!! I get a black screen with this error instead of the familiar boot menu: error: symbol `grub_term_highlight_color' not found grub rescue _ Not only can't I boot ubuntu, I can't boot any other OS I had installed on the computer (namely Windows 8). I am reporting this from another computer. How do I fix it now? Do you test distribution upgrades before releasing them? Well, obviously not enough. And _after_ releasing them, because it's been a f***ing month or two since it was released. At EVERY SINGLE UPGRADE I always get some huge problem that renders my system completely unusable and needs some pretty radical fix. But this is the most f***ed up and low level one ever. At the next upgrade I guess I'll get hardware damage. During the upgrade there was some crash: the system problem detected (or whatever it is called) window popped up, informing of some crash related to VirtualBox (and uslessly offering me the option to report it, just to later tell me it couldn't be reported, as usual with third-party packages). I don't know if that is related and I know that's a third party package, however distribution-upgrade must be rocksolid and it can't brick a whole system just because of a broken package (even assuming that's broken). It must either fix the problem with the package, or offer the option to remove it, or roll back the whole upgrade if it cannot be complete 100% safely. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.4 Architecture: i386 CrashDB: ubuntu Date: Sat May 24 19:48:05 2014 InstallationDate: Installed on 2010-06-23 (1431 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to raring on 2013-08-10 (287 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug dist-upgrade i386 raring ** Changed in: ubuntu-release-upgrader (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/1322890 Title: CRITICAL: 13.10-14.04 upgrade BREAKS GRUP, renders computer UNBOOTABLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1322890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322890] Re: CRITICAL: 13.10-14.04 upgrade BREAKS GRUP, renders computer UNBOOTABLE
*** This bug is a duplicate of bug 1289977 *** https://bugs.launchpad.net/bugs/1289977 And I know you would like me to run apport-collect from the affected machine. I would like to be able to do that too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322890 Title: CRITICAL: 13.10-14.04 upgrade BREAKS GRUP, renders computer UNBOOTABLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1322890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243445] Re: layout (probably CSS) is badly broken
I just installed it with sudo apt-get install phpmyadmin and I did nothing (explicit) to install any third party theme. ** Changed in: phpmyadmin (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243445 Title: layout (probably CSS) is badly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1243445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1243445] Re: layout (probably CSS) is badly broken
If some third party theme not compatible with the version of phpmyadmin got installed automagically, then it must be some packaging issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1243445 Title: layout (probably CSS) is badly broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1243445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318363] [NEW] can't download this youtube video
Public bug reported: $ youtube-dl https://www.youtube.com/watch?v=t0On9tbnKd8 [youtube] Setting language [youtube] t0On9tbnKd8: Downloading video webpage [youtube] t0On9tbnKd8: Downloading video info webpage [youtube] t0On9tbnKd8: Extracting video information [youtube] t0On9tbnKd8: Encrypted signatures detected. ERROR: unable to download video ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: youtube-dl 2013.08.29-1 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun May 11 18:22:27 2014 InstallationDate: Installed on 2013-10-11 (211 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: youtube-dl UpgradeStatus: Upgraded to saucy on 2014-02-23 (77 days ago) ** Affects: youtube-dl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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 1315164] [NEW] list view of Trash content is broken
Public bug reported: Steps to reproduce: - click on the Trash can on the bottom of the Launcher - select list view, as opposed to grid view. It is completely broken and unusable. Main issues: - the default width of the Name column is ridiculously small. Names longer than just 2 or 3 characters show up as ... - columns cannot be resized!! (making the first issue a critical one) - every time the window is moved or resized or it gains or looses focus, the Type column changes its width a few times in a ridiculous dance that lasts about one second Another issue, minor if compared with the above, is that thumbnails are not shown for images, neither in list view nor in grid view. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-20.34-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu May 1 23:28:23 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1299x715+440+143' InstallationDate: Installed on 2013-10-11 (202 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2014-02-23 (67 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315164 Title: list view of Trash content is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1315164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311228] [NEW] Can't connect android debugger any more
Public bug reported: Up to a few hours ago I was able to connect my android phone and debug apps on it from Android studio: - every time I would connect my android phone to the computer via USB, I would get a popup with an error message, something like cannot mound ...something - despite this, Android Studio would see the device and I was able to debug applications on it Starting from now (and I haven't changed anything in my setup): - when I connect the phone, the error message does not show any more - Android studio doesn't detect the device and I can't debug on it. It's as if the device was not connected. adb devices shows an empty list (but I hadn't tried it when it did work) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-19-generic 3.11.0-19.33 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo1974 F pulseaudio Date: Tue Apr 22 18:46:17 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (192 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-19-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-19-generic N/A linux-backports-modules-3.11.0-19-generic N/A linux-firmware 1.116.2 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2014-02-23 (58 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311228 Title: Can't connect android debugger any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311228] Re: Can't connect android debugger any more
Unbelievable. It turns out it's Android's fault. USB debugging turned itself off without a reason or a notice: https://code.google.com/p/android/issues/detail?id=68868thanks=68868ts=1398186474 ** Changed in: linux (Ubuntu) Status: Confirmed = Invalid ** Bug watch added: code.google.com/p/android/issues #68868 http://code.google.com/p/android/issues/detail?id=68868 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311228 Title: Can't connect android debugger any more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239406] Re: cache folder belongs to root, causing firefox to fail to run
@soren-bc I already said which steps produced this bug: - install Ubuntu 13.04 64bit - sudo apt-get install firefox I don't know whether it's reproducible, as I obviously didn't reinstall Ubuntu just to check. ** Changed in: ubuntu Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239406 Title: cache folder belongs to root, causing firefox to fail to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1239406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1239406] Re: cache folder belongs to root, causing firefox to fail to run
If bugs only get looked at when they are 100% systematically reproducible... oh well, that explains a lot of things. Anyway, ok, let's let this expire until somebody else stumbles into in if a few months or years, and so on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1239406 Title: cache folder belongs to root, causing firefox to fail to run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1239406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303082] [NEW] No application menu in Unity
Public bug reported: In Ubuntu 13.10 (Unity), Evince's menu on the top of the screen has only one entry Document Viewer with only one menu item Help, which is pathetic. The full menu is available under a button with a gear wheel icon. Expected: the application's main menu on the top of the screen should contain the full menu. That's what the menu bar is for. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evince 3.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Apr 5 17:52:59 2014 InstallationDate: Installed on 2013-10-11 (175 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: evince UpgradeStatus: Upgraded to saucy on 2014-02-23 (41 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303082 Title: No application menu in Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1303082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296909] Re: What you lock to launcher is not what you get locked to launcher
If the system is generating .desktop files automatically, then it should generate different desktop files for different binaries that are in different locations. What if I run two programs that have absolutely nothing to do with each other but whose executable file happens to have the same name?!? Generating automatically a .desktop file based on a binary name, and reusing that for another binary of the same name, is a wrong design and should be fixed (and the fix is easy). Also, if I download an executable, place it in an arbitrary place, and run it, and then delete it, I don't expect it to leave any trash around the system that will potentially affect other programs. If _it_ does, then it's that executable's author's responsibility, but if the system does, and doesn't warn me, then the system is doing somnething wrong. At least it should show a notice (with a don't show again option) indicating that a desktop file has been created and showing its location, so I know that I may need to delete it later. Consider at least that. And another thing: apparently the .desktop files that are automatically generated for any executable you run, not always work. I downloaded Processing (http://processing.org). It's a .tgz that you extract to a folder and then you run an executable in it. When I run it, an icon appears on the Launcher. Right-clicking and selecting lock to launcher locks the icon lock to the launcher, but when I later click on the icon nothing happens. So the mechanism that creates .desktop files automatically does not always work. I'm marking this bug as invalid because the system is actually working completely as designed. The design is seriously wrong then, and the bug should be reopened until the design is fixed. In this case the problem can be resolved by manually fixing the configuration (.desktop) files that are reserved for the user, probably by removing them. Yes, given that the user figures out that a .desktop file has been created and where. Now I know that, but I had to come here to figure out. That's ridiculous. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296909 Title: What you lock to launcher is not what you get locked to launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1296909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286918] Re: writing to sdcard is unreliable
** Changed in: linux (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286918 Title: writing to sdcard is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286852] Re: Error formatting SD card
** Changed in: linux (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286852 Title: Error formatting SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284342] Re: [REGRESSION Ubuntu 13.10] NumLock LED behavior on external USB keyboard screwed up
** Tags added: kernel-unable-to-test-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Opinion ** Changed in: linux (Ubuntu) Status: Opinion = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284342 Title: [REGRESSION Ubuntu 13.10] NumLock LED behavior on external USB keyboard screwed up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1191551] Re: launcher no longer shows the number of open windows of each icon
I think it's fixed ** Changed in: unity (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1191551 Title: launcher no longer shows the number of open windows of each icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1191551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296909] Re: What you lock to launcher is not what you get locked to launcher
Well, I'm noticing one more general thing that I didn't expect: if I run some arbitrary executable and then right-click on its icon on the launcher and do lock to launcher, it does lock the icon to launcher but that icon is completely useless!!! The lock to launcher function seems to be ill-conceived: it is available for any icon of any running executable, but apparently only works with programs that have been installed in some way. If it is only supposed to work in that case, then this option should not be available at all in other cases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296909 Title: What you lock to launcher is not what you get locked to launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1296909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296909] [NEW] What you lock to launcher is not what you get locked to launcher
Public bug reported: I downloaded Eclipse from here: https://www.eclipse.org/downloads/download.php?file=/technology/epp/downloads/release/kepler/SR2/eclipse-standard-kepler-SR2-linux-gtk-x86_64.tar.gz which is a tar.gz, which I untarred into a custom folder, namely ~/Documents/programmi/eclipse, by placing the .tar.gz in ~/Documents/programmi and right clicking on it with Nautilus and doing extract here. (~/Documents/programmi is not set up to be any special or privileged folder for programs, it's just a folder that I created inside Documents). Then I realized that was not the version of Eclipse I wanted, so I installed Eclipsed by running in a terminal: sudo apt-get install eclipse This created, among other things, a /usr/share/applications/eclipse.desktop file which eclipse outputs /usr/bin/eclipse When I type eclipse into a terminal, the one installed with apt-get will run, as expected. I slightly modified /usr/share/applications/eclipse.desktop so that UBUNTU_MENUPROXY would be used (to work around the menus-not-working bug), and when I run eclipse from a terminal, I can see the menu is affected by the change I made to the .desktop file, so the /usr/share/applications/eclipse.desktop file somehow relates to the executable that is run by writing just eclipse from a command line. When I wrote eclipse into the Dash, the one I had manually downloaded and unzipped would run, which is somewhat funny in itself, because I wonder how it finds the one that I have installed in an arbitrary folder and it doesn't find the one that has been installed with the package manager. Then I did the following: - run eclipse from a terminal (this would run the apt-get installed one) - right click on the icon on the launcher and choose lock to launcher. - exit eclipse - click on the icon that has been created on the launcher Expected: should run the same thing that was running when I locked it to the launcher, which is what I run from a terminal typing eclipse Observed: it runs the one that I had manually downloaded and unzipped. Whatever is going on, there is an inconsistency here. If I run some program, whatever I run it from, and then lock its icon to the launcher, then clicking on that icon must load the program that was running when I locked that icon on the launcher, whatever that is. Not some other version that is installed somewhere else. Then I deleted the folder ~/Documents/programmi/eclipse altogether. Now the icon on the launcher does nothing. Even if I remove it (unlock from launcher), start eclipse again from a terminal (which runs /usr/bin/eclipse), lock it to the launcher again, exit it, even so when I later click on the launcher icon it will launch nothing (as if looking for the one that I deleted). And surprisingly, when I type eclipse into the Dash, it still finds the old one, or at least, it finds something that won't run if I click on it. Even after restarting the computer. The only file named eclipse.desktop in the entire filesystem is the one under /usr/share/applications/eclipse.desktop It's as if by merely unzipping the .tar.gz file into an arbitrary non-standard folder, some kind of shortcut to it has been installed somewhere that allows it to be found when typing Eclipse into the Dash; even if I didn't install any package, just unzipped a .tar.gz file. Even after deleting the unzipped folder, that link somehow persists somewhere. It's crazy. And it even takes the place of the icon that I lock to Launcher when running /usr/bin/eclipse. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Mar 24 20:08:39 2014 InstallationDate: Installed on 2013-10-11 (164 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2014-02-23 (29 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296909 Title: What you lock to launcher is not what you get locked to launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1296909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296909] Re: What you lock to launcher is not what you get locked to launcher
Oh, yes, there it is. It doesn't show up with sudo find / -name eclipse.desktop, that's why I couldn't find it. One mistery is how it got created (but maybe Eclipse itself, the one I unzipped manually, created it when run the first time). Anyway, if you run some executable, then you right-click on its icon and lock it to the launcher, and the result is that the icon locked to the launcher calls some unrelated .desktop file somewhere else, that's a wrong behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296909 Title: What you lock to launcher is not what you get locked to launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1296909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296958] [NEW] This error message lacks the most basic information
Public bug reported: See the screenshot. Error messages like this enrage me. The update information is outdated. This may be caused by bla bla bla (another thing that enrages me is an error message that I cannot copy and paste). This tells me that there is a problem and doesn't give me the most basic information I need to fix it: what repository or file could not be reached. It then says Please update manually by selecting Show Updates bla bla bla. If I do so, I would expect to be able to finally see which repository is failing, but no: i just get a popup that says your computer is up to date. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: update-manager 1:0.194.1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Mar 24 22:17:19 2014 GsettingsChanges: b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'launch-time' b'1395695631' InstallationDate: Installed on 2013-10-11 (164 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: Upgraded to saucy on 2014-02-23 (29 days ago) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: Screenshot from 2014-03-24 22:14:37.png https://bugs.launchpad.net/bugs/1296958/+attachment/4041508/+files/Screenshot%20from%202014-03-24%2022%3A14%3A37.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296958 Title: This error message lacks the most basic information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1296958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1296253] [NEW] At random times, Launcher does not respond to clicks too close to the left border of the screen
Public bug reported: I have Launcher set up to not automatically hide (because it's buggy and it would stop showing up too often). Usually, you can click on a launcher icon even on the leftmost column of pixels and it will respond to clicks. Sometimes however, randomly, if you click on the very leftmost region, i.e. just next to the left border of the screen, it will not respond to click; you then have to click a little bit more to the right, inside the rounded rectangle that surrounds the icon, for it to work. Then, after doing some random things with the mouse (switching focus between different windows, closing some), it behaves normally again ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Mar 23 12:19:12 2014 InstallationDate: Installed on 2013-10-11 (162 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2014-02-23 (28 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1296253 Title: At random times, Launcher does not respond to clicks too close to the left border of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1296253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295778] [NEW] Nautilus definitely needs to be repleced
Public bug reported: Now this is too much. I wanted to temporarily see a folder tree in TREE VIEW and I've found out that feature has been REMOVED. That's absolutely ridiculous. Who on earth, in his right mind, would decide to remove such a feature from a file browser, which was already implemented? This is one more proof, if any more was needed, that the development of Nautilus has (since a pretty long time ago now) taken a completely demential drift. Recent changes in Nautilus have all been for the worse: regressions, design decisions that can only be described as stupid, removal of obvious features without any benefit in exchange. The file browser is a pretty important part of an operating system. If Ubuntu wants to remain a usable operating system, it's urgent to drop Nautilus in favour of something else whose main developers upstream are not on drugs. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Fri Mar 21 18:35:25 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1299x715+359+210' InstallationDate: Installed on 2013-10-11 (161 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2014-02-23 (26 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Summary changed: - Tree view gone + Nautilus definitely needs to be repleced -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295778 Title: Nautilus definitely needs to be repleced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1295778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277888] Re: In most apps all menu items are gray / unclickable
Oh, ok, this one works for me: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1263205/comments/7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277888 Title: In most apps all menu items are gray / unclickable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1277888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277888] Re: In most apps all menu items are gray / unclickable
For god's sake, this is huge. Any workaround? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277888 Title: In most apps all menu items are gray / unclickable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1277888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213961] Re: The new search feature is a huge step backwards in usability
By Ubuntu has patched typeahead selection back in you mean it will become available in some future update, right? Because currently I don't see typeahead selection. Typing results in a search (which also includes subfolders). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213961 Title: The new search feature is a huge step backwards in usability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1213961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1164016] Re: restore type-ahead find
I totally second comments #90 and #91 This bug demonstrates (if any more proof was needed) that Nautilus needs to be replaced with something else by default in Ubuntu (and in any distro trying to be of any use), quite urgently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286852] Re: Error formatting SD card
Sorry, it would not be possible for me to test the latest upstream kernel. ** Tags added: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286852 Title: Error formatting SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286912] Re: can't mount SD card more than once
Sorry, it would not be possible for me to test the latest upstream kernel. ** Tags added: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286912 Title: can't mount SD card more than once To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286918] Re: writing to sdcard is unreliable
Sorry, it would not be possible for me to test the latest upstream kernel ** Tags added: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286918 Title: writing to sdcard is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286852] [NEW] Error formatting SD card
Public bug reported: I inserted a SD card into the SD card reader of my laptop. I ran Disks from the Dash, I selected the SD card from the list of units, I selected a partition, I clicked format and selected the fat filesystem type. After a few minutes of waiting with a frozen waiting supposed-to-be- animation icon, a popup showed up with this error: Error formatting volume. Error synchronizing after formatting with type `vfat': Timed out waiting for object (udisks-error-quark, 0) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-17-generic 3.11.0-17.31 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2137 F pulseaudio Date: Sun Mar 2 18:10:05 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (141 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-17-generic N/A linux-backports-modules-3.11.0-17-generic N/A linux-firmware 1.116.2 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2014-02-23 (7 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286852 Title: Error formatting SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286852] Re: Error formatting SD card
And now, after removing the SD card from the reader and inserting it again, it doesn't even show up under devices. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286852 Title: Error formatting SD card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286856] [NEW] [13.10 Regression] External screen configuration wrong in login screen
Public bug reported: I have an external monitor that I usually connect to my laptop. It's configured to be the only screen, so when I plug it in, the laptop's builtin screen automagically turns off and the external screen becomes the primary and only screen, and when I unplug it, the builtin screen turns on and becomes the only screen. So far so good. In 13.04, this used to apply also to the Ubuntu login screen, that is for example, if I turned on the computer with the external monitor already connected, I would see the login screen on the external monitor only. Since I upgraded to 13.10, when the login screen appears and the external monitor is connected, the screen shows as an extended screen, so that the login box is only visible on the builtin screen and the external monitor is empty (with a background image). After logging in, it switches to the correct configuration (i.e. the builtin screen turns off and the external screen becomes the primary one). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Mar 2 18:18:00 2014 InstallationDate: Installed on 2013-10-11 (141 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2014-02-23 (7 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286856 Title: [13.10 Regression] External screen configuration wrong in login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1286856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286912] [NEW] can't mount SD card more than once
Public bug reported: - plug an SD card into the laptop's card reader - it mounts automatically and I can see it in Nautilus - eject it with the eject button in nautilus - remove it - plug it in again expected: should automount again Observed: does nothing I have to reboot in order to see the sd card again. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-17-generic 3.11.0-17.31 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2152 F pulseaudio Date: Sun Mar 2 22:19:48 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (142 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-17-generic N/A linux-backports-modules-3.11.0-17-generic N/A linux-firmware 1.116.2 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2014-02-23 (7 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286912 Title: can't mount SD card more than once To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995743] Re: 197b:2394 Internal SD card reader is not working on Dell XPS 17 L502X
My Acer Aspire V3-571G does detect and mount the SD card when inserted but ONLY THE FIRST TIME. After ejecting and removing it, when I insert it again nothing will happen. The suggested pci rescan workaround does not work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995743 Title: 197b:2394 Internal SD card reader is not working on Dell XPS 17 L502X To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/995743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286918] [NEW] writing to sdcard is unreliable
Public bug reported: - I plugged an SD card into the SD card reader - I copied a file with Nautilus from my Desktop to the SDCard by dragging and dropping it = it seemed to copy fine, with no error message - When done, I ejected the SDCard by clicking on the eject-like button in Nautilus = I got a message that said Writing data. Don't remove the device until finished = then another message which I don't remember exactly but it said it was now ok to remove the device - I removed the SDCard After that, the file on the SDcard was 0bytes in sized, which I only found out when I tried to use it on a smartohone. That a 92Mb file could not be copied without error is already bad, but what is absolutely disastrous is that the error didn't even get detected and no error message was ever shown either when copying the file or when removing the sd card. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-17-generic 3.11.0-17.31 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2187 F pulseaudio Date: Sun Mar 2 22:32:46 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (142 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-17-generic N/A linux-backports-modules-3.11.0-17-generic N/A linux-firmware 1.116.2 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2014-02-23 (7 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286918 Title: writing to sdcard is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286918] Re: writing to sdcard is unreliable
Later, I tried to copy the file again. This time, the progress bar got stuck very close to 100% (after progressing very quickly from 0% to almost 100%) and got frozen there forever. After waiting several minutes, I clicked on the x next to the progress bar to cancel the copying operation, but the window with the progress never closed (the cancel button is now greyed out). That never works, by the way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286918 Title: writing to sdcard is unreliable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286584] [NEW] Details take too long to unfold in crash reporter popup
Public bug reported: When some program crashes in Ubuntu and a popup shows up informing you of that and asking whether to send a bug report about the crash, there is a Details button (or link). If you click it, it can take several minutes for the details to show, even when they turn out to be just a dozen of lines of text or so. There's no way such a long time can be necessary. There is certainly something wrong about it. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport 2.12.5-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportLog: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Mar 1 19:05:44 2014 InstallationDate: Installed on 2013-10-11 (141 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to saucy on 2014-02-23 (6 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286584 Title: Details take too long to unfold in crash reporter popup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1286584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286621] [NEW] bluetooth keeps turning off
Public bug reported: Bluetooth turned off (without me turning it off), as it already happened a lot of times. Now i can't turn it on. I run Bluetooth from the Dash, I turn on Bluetooth with the On/Off button. Then it goes back to off. It will probably work after reboot. Just one more bluetooth bug making bluetooth completely unusable under Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Mar 1 22:21:46 2014 InstallationDate: Installed on 2013-10-11 (141 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (6 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: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286621 Title: bluetooth keeps turning off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1286621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286621] Re: bluetooth keeps turning off
Actually, even after reboot, bluetooth still kept turning itself off. I got it to work again only by turning it physically off and on via hardware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286621 Title: bluetooth keeps turning off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1286621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283822] Re: clock disappeared from notification area
No, it isn't. It simply happened. ** Changed in: indicator-datetime Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283822 Title: clock disappeared from notification area To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1283822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284308] [NEW] Bogus another operation in progress error. Can't copy files from a bluetooth device
Public bug reported: I have upgraded to Ubuntu 13.10. And as usual, with the upgrade, a whole new bluetooth issue, which this times makes transferring files from the phone to the computer (which already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose bluetooth settings 3 - select the phone among the listed devices 4 - click on Browse files 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer = I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is another operation in progress. Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then ejected the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error This location could not be displayed. Another operation in progress, so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when ejecting the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 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:44318 acl:198 sco:0 events:355 errors:0 Â Â TX bytes:6132 acl:178 sco:0 commands:82 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: Screenshot from 2014-02-24 21:23:45.png https://bugs.launchpad.net/bugs/1284308/+attachment/3994909/+files/Screenshot%20from%202014-02-24%2021%3A23%3A45.png -- 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 1284308] Re: Bogus another operation in progress error. Can't copy files from a bluetooth device
** Attachment added: Screenshot from 2014-02-24 21:34:36.png https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1284308/+attachment/3994923/+files/Screenshot%20from%202014-02-24%2021%3A34%3A36.png ** Description changed: - I have upgraded to Ubuntu 13.10, and I also have a new Android phone, - obviously with bluetooth. + I have upgraded to Ubuntu 13.10. - And now here comes a whole new bluetooth issue, which makes transferring - files from the phone to the computer (which already was painful) - completely impossible! + And as usual, with the upgrade, a whole new bluetooth issue, which this + times makes transferring files from the phone to the computer (which + already was painful) completely impossible! How I reproduce (100% systematic): 1 - click on the Bluetooth icon in the notification area 2 - from the dropdown menu, choose bluetooth settings 3 - select the phone among the listed devices 4 - click on Browse files 5 - A Nautilus windows opens, allowing me to browse files on the phone. Open the DCIM/Camera folder 6 - Select a couple of files. Either drag and drop them, or copy and then paste them, into a folder on the computer = I systematically get an error, but it can be any of the two variants shown in the two screenshots (one says there was an error copying the file, the other says there was an error getting information about the file; in both cases the given reason is another operation in progress. Note also that in one case there is a Retry button, in the other there is not - pure nonsense). I then ejected the phone with the eject button next to its name in Nautilus, and repeated the whole process. I randomly get any of three outcomes: - the one described above (MOST of the times) - at step 4, I get an error This location could not be displayed. Another operation in progress, so I cannot even browse files or - at some point (not sure whether it was at step 4 above or when ejecting the phone) something CRASHES (I get the usual Ubuntu message informing me of that). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 21:24:05 2014 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 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:44318 acl:198 sco:0 events:355 errors:0 - TX bytes:6132 acl:178 sco:0 commands:82 errors:0 + Â 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:44318 acl:198 sco:0 events:355 errors:0 + Â Â TX bytes:6132 acl:178 sco:0 commands:82 errors:0 -- 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 1284308] Re: Bogus another operation in progress error. Can't copy files from a bluetooth device
If you wonder why I go through the trouble of browsing files on the phone from the computer and fetching them, instead of sending them from the phone to the computer, that's because if I send them, they get systematically rejected, a regression that appeared back in 13.04 or 12.10 (it used to work before). Browsing files from the computer and copying them used to work, until I upgraded to 13.10 -- 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 1250186] Re: caps lock state feedback is not sent to keyboard led when plugged (NumLock IS, which is ok). Neither CapsLock nor NumLock feedback is sent to led when state changes (e.g. by other
** Changed in: linux (Ubuntu) Status: Expired = Fix Released ** Changed in: linux (Ubuntu) Status: Fix Released = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250186 Title: caps lock state feedback is not sent to keyboard led when plugged (NumLock IS, which is ok). Neither CapsLock nor NumLock feedback is sent to led when state changes (e.g. by other keyboard) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284342] [NEW] [REGRESSION Ubuntu 13.10] NumLock LED behavior on external USB keyboard screwed up
Public bug reported: After upgrading from Ubuntu 13.04 to 13.10, issue #1250186 with the Caps Lock LED is fixed, and now NumLock, which used to work (almost) correctly, is srewed up, suffering from exactly the same issue as CapsLock used to. Steps to reproduce: - plug an external USB keyboard - turn on NumLock on that keyboard = the keyboard's NumLock LED turns on, and the numeric keys start working as numbers, as expected - now unplug the keyboard - replug the keyboard = Expected: the LED status must be consistent with the actual behavior. And it used to be!! It used to work in the best possible way: numlock status USED TO BE REMEMBERED, and the LED status was updated when replugging the keyboard, so after unplug/replug the behavior was as before and the displayed status was consistent with it. = Observed: the actual NumLock status is remembered, meaning the numeric keys keep working as number keys, as if num lock was ON, which is how it was prior to unplug/replug. But the LED is now off, so it is inconsistent with reality. The fact that the upgrade from 13.04 to 13.10 has fixed #1250186 and has screwed up NumLock behavior which was OK (on the same computer and same external keyboard), demonstrates that both are 100% software issues, i.e. Ubuntu issues, not hardware ones. And that correct behavior can be achieved. The only thing that was already wrong with NumLock, and remains wrong after the upgrade, is that the external keyboard's LED status is not updated when the NumLock status is changed from the laptop's builtin keyboard's NumLock key, while the behavior is always the same for both keyboards (leds behave as if keyboard were independent, but they are not). However, this provides a workaround for the bug, so it must NOT be changed before the bug is fixed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-17-generic 3.11.0-17.31 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2186 F pulseaudio Date: Mon Feb 24 22:18:44 2014 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (136 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-17-generic N/A linux-backports-modules-3.11.0-17-generic N/A linux-firmware 1.116.2 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284342 Title: [REGRESSION Ubuntu 13.10] NumLock LED behavior on external USB keyboard screwed up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250186] Re: caps lock state feedback is not sent to keyboard led when plugged (NumLock IS, which is ok). Neither CapsLock nor NumLock feedback is sent to led when state changes (e.g. by other
The caps lock state feedback is not sent to keyboard led when plugged. part is now fixed on 13.10. But now NumLock, which used to work, is screwed up. Great. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284342 The Neither CapsLock nor NumLock feedback is sent to led when state changes (e.g. by other keyboard) part remains. Which actually provides a workaround for 1284342 right now. Bug 1284342 tracks the NumLock regression. If this one is going to track the missing-feadback-for-both-capslock-and-numlock issue, then here's the expected behavior: EITHER numlock and capslock status feedback should propagate to ALL connected keyboards when it changes, OR each keyboard should have its individual numlock and capslock state, independent of other keyboards, so that, even if the feedback does not propagate to other keyboards, the status shown on the led would always be consistent with the actual behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250186 Title: caps lock state feedback is not sent to keyboard led when plugged (NumLock IS, which is ok). Neither CapsLock nor NumLock feedback is sent to led when state changes (e.g. by other keyboard) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250186] Re: Neither CapsLock nor NumLock feedback is sent to led when state changes (e.g. by other keyboard)
** Summary changed: - caps lock state feedback is not sent to keyboard led when plugged (NumLock IS, which is ok). Neither CapsLock nor NumLock feedback is sent to led when state changes (e.g. by other keyboard) + Neither CapsLock nor NumLock feedback is sent to led when state changes (e.g. by other keyboard) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250186 Title: Neither CapsLock nor NumLock feedback is sent to led when state changes (e.g. by other keyboard) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284342] Re: [REGRESSION Ubuntu 13.10] NumLock LED behavior on external USB keyboard screwed up
Sorry, no, it would not be possible for me to test the mainline kernel. If it is for you, however, it should be pretty straight-forward to check whether the issue is present or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284342 Title: [REGRESSION Ubuntu 13.10] NumLock LED behavior on external USB keyboard screwed up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283822] [NEW] clock disappeared from notification area
Public bug reported: Suddenly I realized the clock was not there, where it usally is, on the top-right corner of the screen. I dono't know how long it was since it had disappeared; however I had restarted the computer no more than a few minutes earlier. After reboot, the clock is there again as expected. Maybe the clock widget crashed? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Feb 23 22:05:17 2014 InstallationDate: Installed on 2013-10-11 (135 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2014-02-23 (0 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283822 Title: clock disappeared from notification area To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1283822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283578] [NEW] Confirmation window needlessly exceeds screen height and cannot be resized. Access to the vital buttons is difficult
Public bug reported: While doing the distribution upgrade from 13.04 to 13.10, after the Preparing to upgrade and Setting new software channels phases were finished and before the Getting new packages one started, a window popped up with the usual information and warnings. After I clicked on the Details button, the the window expanded to a height much bigger than necessary (that is, there was plenty of empty space in it; perhaps this was the height that would be needed if all of the collapsed-by-default items in the Details box were to be unfolded). exceeding total screen height. This is the first fault: window height should only expand as needed and _always_ be kept within the area of the screen (if more is needed, then it must have a scroller). The buttons to proceed or cancel were both outside the screen, below the bottom. Furthermore, the window could not be resized in height. Usually you can reduce (or increase) the height of a window by dragging its top border. In this case the top border would act as a handle but you could not drag it downwards, as if the window was at its minimum height and could not be shrinked. This is the second fault: no matter what, you must be able to resize this window. If you resize it to a size too small to contain all the content, then a scroller should appear. After a few seconds of panic, I realised I could move the window upwards by alt-clicking on it and dragging it. This way I could access its continue button. Not a big deal but definitely a usability bug. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.13 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CrashDB: ubuntu Date: Sat Feb 22 23:34:57 2014 InstallationDate: Installed on 2013-10-11 (134 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to raring on 2014-02-22 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade raring ** Summary changed: - Confirmation window needlessly exceeds screen height and cannot be easily resized + Confirmation window needlessly exceeds screen height and cannot be resized. Access to the vital buttons is difficult -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283578 Title: Confirmation window needlessly exceeds screen height and cannot be resized. Access to the vital buttons is difficult To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1283578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher
And when you know it's intentional it is annoying as well as surprising :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263786 Title: Nonsense behavior of scrollwheel over Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1263786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278938] [NEW] system became unusable after resume from hibernation
Public bug reported: I resumed from hibernation. All the windows would respond to some kinds of interaction, but not others. For example: + I could bring a window to front by clicking on its launcher icon + I could unmaximize the frontmost maximized window by clicking on the top of the screen and dragging it downwards, - however I could not move around a window by dragging its title bar, - nor by alt-clicking inside the window and dragging - nor could I close a window by clicking on its close button, + I could switch window with alt+tab - but not by clicking on any window + I could initiate quitting a program by using its File menu - quit, or by right-clicking on its launcher icon and choosing quit - but once the popup window appeared asking me whether to save or discard changes or cancel, none of the buttons would respond to clicks No process was consuming a relative amount of cpu. This got fixed only by rebooting. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Feb 11 16:28:42 2014 InstallationDate: Installed on 2013-10-11 (122 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278938 Title: system became unusable after resume from hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1278938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277180] [NEW] dotted rectangles remain drawn in window after copying a bunch of files
Public bug reported: I copyed a bunch of files from a Nautilus window into another by Ctrl+dragging and dropping them. Both windows were set with icons visualization, so when I (ctrl)dragged and dropped the icons, dotted rectangles were drawn and dragged, as expected. However, after dropping the files, which were succesfully copied, the dotted rectangles should have disappeared, but they remained, as if printed on the destination window. Neither by moving, nor by minimizing and remaximizing the window, could I get rid of the spurious dotted rectangles. Even while navigating to other folders, the dotted rectangles stay there. Even after resizing the window. Despite the contents of the window being redrawn and updated, the dotted rectangles are still there, and they move around while I move around the window, as if they were part of its contents. The only way to have them disappear is to completely close the window. Obviously this is not systematically reproducible. This doesn't happen often. Don't expect to be able to reproduce it by ctrl+dragging icons from a window to another. 99.99% of the times this won't happen. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Thu Feb 6 18:15:28 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1059x698+434+254' InstallationDate: Installed on 2013-10-11 (117 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1277180 Title: dotted rectangles remain drawn in window after copying a bunch of files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1277180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271532] [NEW] Screenshots randomly empty
Public bug reported: I'm almost sure this is a regression, as I often take a lot of screenshots and I had never seen this until very recently (a few days). At random times, all the screenshots I take using the PrintScreen key start being empty, meaning they only produce an empty image of the size of the screen all of a uniform color (f2f1f0). Starting from that, every single screenshot is empty, until some random action I take, such as switching windows, fixes the issue. This last time what fixed the issue was: - I ran the Screenshot application manually from the dash (instead of hitting the PrintScreen key as I normally do), and it worked fine - then I tried again with the PrintScreen key and now it worked. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jan 22 13:57:03 2014 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.8.0-32-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-33-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-34-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / 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 (102 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.7-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.7-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Tue Jan 21 19:23:48 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6.2 xserver.video_driver: intel ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271532 Title: Screenshots randomly empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1271532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271532] Re: Screenshots randomly empty
Now it's happening again and I can't figure out how to fix it. Running the Screenshot app from Dash doesn't help this time, nor does switching windows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271532 Title: Screenshots randomly empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1271532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1270626] [NEW] Cannot print until reboot after cancelling a job
Public bug reported: What I did: - From Libre Office, sent a job to the printer (i.e. printed a document). The printer wouldn't print because it was out of color ink, so I decided to print in grayscale - I sent a second job to the printer (printing in greyscale) but I had forgotten to cancel the first one. So there was one job in the processing state and another in the pending state. So far so good. - I cancelled the job being printed and I hit the X button on the very printer, so as to physically cancell it from the printer as well. Expected: the pending job should start being printed. Observed: nothing happened. The second job remained pending So: - I cancelled the pending job as well. Now there was no pending nor printing job. - I turned off the printer. I disconnected and reconnected the printer to power, I turned it on again. - I turned on the printer - I tried printing a new document Expected: the document should be printed and listed as printing in the job list Observed: nothing happened. The new job was listed as pending since the very beginning. - So I cancelled the pending job, and I also switched off and on the printer again. - I opened Printers. I right-clicked on the printer's icon and chose properties Expected: the printer status should be idle Observed: the printer status was Printing page 1 or something like that (while there was no item in the job list). - I rebooted - I printed a new document Observed: printer worked as expected and printed the document. So there are situations where even after cancelling all printing jobs, somehow the printer remains in the wrong state as if it was printing something, while it isn't, and any new job that you send remains in the pending state forever and there's no way to get the printer to work again until a reboot. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cups 1.6.2-1ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Sun Jan 19 20:00:17 2014 InstallationDate: Installed on 2013-10-11 (100 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Lpstat: device for HP-Photosmart-C6200-series: hp:/usb/Photosmart_C6200_series?serial=MY7B6H51S40506 device for HP_DeskJet_940C: hp:/usb/DeskJet_940C?serial=MY17O671S5BH MachineType: Acer Aspire V3-571G MarkForUpload: True Papersize: a4 PpdFiles: HP-Photosmart-C6200-series: HP Photosmart c6200 Series, hpcups 3.13.3 HP_DeskJet_940C: HP Deskjet 940c, hpcups 3.13.3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1270626 Title: Cannot print until reboot after cancelling a job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1270626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262308] Re: Printing has become super slow. Worked before
You seem to assume that when the slow printing occurs, some printing-related process wold be consuming a lot of CPU. That is not the case. I've just observed a superslow printing. It would print a line, then wait like 10 seconds, then print another line, etc. By the time I had found this bug report again (because I remembered you asked me to post the output of some command if it occurred again) printing was already finished. So I couldn't check top (which now I know is what I was supposed to check), but I can tell cpu usage had not become high because when it does, I notice the increase in the cooler fan speed. I printed another document so that I could try what you ask but then the printing happened at a normal speed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262308 Title: Printing has become super slow. Worked before To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1262308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher
No, this is not the opposite of that at all. Please read the description of that request more carefully: (emphasys added) Title: Launcher, Window Management - More Effective window switching FOR APPS WITH MULTIPLE WINDOWS using the Launcher Description: It would be very useful if you could simply hover over an icon of an open app and scroll with the mouse wheel to switch and highlight BETWEEN THE WINDOWS OF THAT APP, *IF IT HAS MORE*. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263786 Title: Nonsense behavior of scrollwheel over Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1263786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081843] Re: [FFe] Launcher, Window Management - More Effective window switching for apps with multiple windows using the Launcher
Note that the implementation of this feature is broken. See https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1263786 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081843 Title: [FFe] Launcher, Window Management - More Effective window switching for apps with multiple windows using the Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1081843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081843] Re: [FFe] Launcher, Window Management - More Effective window switching for apps with multiple windows using the Launcher
It's broken in that: 1 - if you hover the icon of an app OTHER THAN THE ONE CURRENTLY FOCUSED and move the scrollwheel, you'll steal focus from the currently focused app and give it to another. And that is not reversible by moving back the scrollwheel. In other words, this should only work on the icon of the app that currently has focus. . And as a special case particularly annoying: 2 - this even happens if you hover on an icon of an app that HAS ONLY ONE WINDOW and move the scrollwheel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081843 Title: [FFe] Launcher, Window Management - More Effective window switching for apps with multiple windows using the Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1081843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher
That requirement is not complete. It should be changed to: If the application is not running, or has only one open window, OR IS NOT FOCUSED, mouse wheel clicking towards or away from the user when the pointer is over the application's launcher icon should do nothing. Mouse wheel should only allow switching windows between an already focused app. Or, a completely different acceptable alternative to the current behavior, would be that mouse wheel over the launcher (regardless of which icon the cursor is on) would switch among _all_ open windows, of all apps. What is definitely wrong is that: - you move the cursor over an app that doesn't have focus (whether or not it has more than one window) - you move the mouse wheel = some window of that app gets focus stealing focus from the current app. Then the wheel will only allow you to switch between windows of that newly focused app but you won't be able to go back to the previously focused app by reversing your mouse wheel movement. All this can is even implicit in the words switch between. Switching between open windows of an app means switch from an open window of that app to another open window of that app. So, if focus is not on any window of that app in the first place, moving the mouse wheel while the cursor is over its icon should do nothing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263786 Title: Nonsense behavior of scrollwheel over Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1263786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher
If the application *is not* in focus when the user moves their pointer over the Launcher app icon, the first mouse wheel click towards or away from the user should focus the application, and bring the top most window in the application's z stack to the front of the global z stack. OMFG, I can't believe that was by design. That's simply demential. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263786 Title: Nonsense behavior of scrollwheel over Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1263786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher
By the way, this is not really accurate: your bug here only describes the case about one and only one window open, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263786 Title: Nonsense behavior of scrollwheel over Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1263786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1081843] Re: [FFe] Launcher, Window Management - More Effective window switching for apps with multiple windows using the Launcher
Oh my god, point (1) was by design! If the application *is not* in focus when the user moves their pointer over the Launcher app icon, the first mouse wheel click towards or away from the user should focus the application, and bring the top most window in the application's z stack to the front of the global z stack. Subsequent clicks of the mouse wheel the operate exactly as described above For god's sake, this part needs to be reconsidered. There is a basic principle in the way mouse wheel interaction has ALWAYS worked EVERYWHERE and you're breaking it here, and it's not a good innovation. The mousewheel is used to move something forward and backward, and if you move it forwards and then backwards (or viceversa) of an equal amount, you go back to the original status. Think about the way it is used for scrolling a page, or zooming in and out in an image editor, or (I hate it but unfortunately it's become widespread) switching between tabs in a browser, or between choices in a dropdown menu (even without unfolding it, regrettably, but again that's become popular). In all cases, the rule is never broken: if you move one step too much in one direction, either intentionally or accidentally (the latter being very common) you can always go back by moving the wheel one step in the following direction. Now even if point 2 gets fixed , which is clearly a bug and contraddicts the requirements stated in this request (see #1263786), you are still breaking the reversibility of mouse wheel movements. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1081843 Title: [FFe] Launcher, Window Management - More Effective window switching for apps with multiple windows using the Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1081843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209035] Re: Whole system frozen, had to hard power off
I get the impression that reporting bugs as a user is a complete waste of time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209035 Title: Whole system frozen, had to hard power off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1209035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1079848] Re: pae kernel corrupts nvidia driver
I don't have that computer any more. I installed the nvidia drivers in what I believe was the standard way in Ubuntu, i.e. through some Settings panel which was called something like Additional Drivers I seem to remember. I can't find that any more on Ubuntu 13.04 (on my new computer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1079848 Title: pae kernel corrupts nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1079848] Re: pae kernel corrupts nvidia driver
This is a little bit ridiculous. The fact that I don't have the hardware any more doesn't mean the bug has disappeared, and as per comment #4 there seems to be enough information here to fix the issue or at least investigate it further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1079848 Title: pae kernel corrupts nvidia driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1079848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1264280] [NEW] Cannot browse file on bluetooth device. Nonsense error message
Public bug reported: Usually I can browse files on my mobile connected via bluetooth from the computer. Same computer, same phone, now I can't. - Click on the bluetooth icon on the notification area - select bluetooth settings (directly selecting Browse files within the submenu under the name of the device wouldn't work, as per bug #1254106) - select the device which is the only one in the list and click Browse files. = I get this nonsense error message: Unable to find the requested file. Please check the spelling and try again And below: Unhandled error message: Unable to load location. Note the error message suggesting to check the spelling is particularly stupid as no typing is involved in the process. I've done a hcidump during the process and it is COMPLETELY EMPTY. I have removed the phone from the devices, paired it again from scratch, and it does not fix the issue. It used to work until very few days ago. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Thu Dec 26 12:04:18 2013 InstallationDate: Installed on 2013-10-11 (75 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer 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:5507 acl:73 sco:0 events:209 errors:0 TX bytes:3114 acl:76 sco:0 commands:69 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1264280 Title: Cannot browse file on bluetooth device. Nonsense error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1264280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1264280] Re: Cannot browse file on bluetooth device. Nonsense error message
After this, I noticed that the mobile device was listed on the bottom of the left panel of Nautilus. So I clicked it, and Nautilus crashed. After that, I relaunched Nautilus, and now browsing the mobile device works both from Nautilus (clicking on the device name on the left panel) and from the Bluetooth application (following the steps in the report) After this, when I open Nautilus, it generates a new icon in the Launcher instead of just adding an arrow on the left of the existing launcher icon. There's certainly a bug in Nautilus as it crashed; I don't know if it's _only_ nautilus or if bluetooth has an issue as well. ** Package changed: bluez (Ubuntu) = nautilus (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1264280 Title: Cannot browse file on bluetooth device. Nonsense error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1264280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1264152] [NEW] Syntax highlight: nonsense pink coloring of portions of expressions in JS
Public bug reported: See screenshot. This is a JS file. There are portions of expressions that are incorrectly highlighted in pink as if they were strings. There is no syntax error before or after the captured portion of text. The script is parsed as expected by the javascript interpreter, so the syntax highlight is wrong. Oh my *** god, I see what the problem is!! The portion between / and / are highlighted as if they were regular expressions. But they aren't, nor does the parser of the language interpreter interpret them as such, so the syntax highlighting is wrong. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Wed Dec 25 21:16:41 2013 InstallationDate: Installed on 2013-10-11 (75 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1264152 Title: Syntax highlight: nonsense pink coloring of portions of expressions in JS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1264152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1264152] Re: Syntax highlight: nonsense pink coloring of portions of expressions in JS
** Attachment added: Screenshot illustraring issue https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1264152/+attachment/3935611/+files/Screenshot%20from%202013-12-25%2021%3A16%3A28.png ** Description changed: See screenshot. This is a JS file. There are portions of expressions that are incorrectly highlighted in pink as if they were strings. There is no syntax error before or after the captured portion of text. The script is parsed as expected by the javascript interpreter, so the syntax highlight is wrong. - Oh my *** god, I see what the problem is!! The portion between / and / are highlighted as if they were regular expressions. But they aren't, nor does the parser of the language interpreter - interpret them as such, nor does the standard say they should, so the - syntax highlighting is wrong. + interpret them as such, so the syntax highlighting is wrong. - - Couldn't GEdit just use the same language definitions that are actually used by true languages (I guess most of them are available as open source), so that you don't have to rewrite definitions to emulate the behavior of language parsers? Gedit is FULL of bugs like these (see how it wrongly parses PHP within HTML, for example), so if it could just take language definitions from true parsers, maybe we would finally get rid of all these syntax highlight annoyances at once. Or is that not feasible? ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Wed Dec 25 21:16:41 2013 InstallationDate: Installed on 2013-10-11 (75 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gedit UpgradeStatus: No upgrade log present (probably 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/1264152 Title: Syntax highlight: nonsense pink coloring of portions of expressions in JS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1264152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1264152] Re: Syntax highlight (JS): Portions of expressions between / and / taken as regular expressions
** Summary changed: - Syntax highlight: nonsense pink coloring of portions of expressions in JS + Syntax highlight (JS): Portions of expressions between / and / taken as regular expressions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1264152 Title: Syntax highlight (JS): Portions of expressions between / and / taken as regular expressions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1264152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263786] Re: Nonsense behavior of scrollwheel over Launcher
According to your reasoning, and as I already mentioned in my report, the current behavior makes perfect sense WHEN THE ICON HAS MORE THAN ONE WINDOW and one of them is already the one with focus. That is: put the mouse cursor on an icon that has more than one window, one of which has already focus. Move the scrollwheel. It switches windows. Ok, makes sense (given the use the mouse wheel to switch between multiple-data display element in a GUI, which is a shitty way of using the mouse wheel that regretfully has become widespread, but if we accept that, it's consistent). Now put the mouse cursor on a random icon on the launcher which has only one window (there's no data elements to switch between at all). Move the mouse wheel = that window gets focus, and you can't give focus back to the window that previously had it unless you look for it and click on it. That does not make sense and it is an annoyance. You don't expect the current application to be switched without a positive click: well that's exactly what happens: current application is switched with just a movement of the mouse wheel over the icon of another application. Having the mousewheel cycle through icons in the whole launcher would make as much sense as it makes to cycle through tabs within a window when you place the mouse cursor over any tab of e.g. Google Chrome or Ubuntu's Terminal and move the scrollwheel: something that I hate and I would happily get rid of, but it is kind of consistent in that, if you do that by accident, you can go back by moving the wheel back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263786 Title: Nonsense behavior of scrollwheel over Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1263786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263786] [NEW] Nonsense behavior of scrollwheel over Launcher
Public bug reported: Steps to reproduce: - move the mouse cursor over the launcher - move it over the icon of an application that has one and only one window open that is not on front - move the scrollwheel of the mouse in any direction Expected behavior: NOTHING. Ovserved behavior: the window, corresponding to the icon over which the mouse cursor is, is brought to front; and this cannot be reversed easily. Trying it with an icon of an application that has two or more windows open reveals why this happens: - move the mouse cursor over the Launcher over an icon of an application that has two or more windows open - move the scrollwheel This will switch between windows of that application, so scrolling up or down will bring one or another window (of that same application) to front. This is already annoying, like many other abuses of the scrollwheel that unfortunately have become widespread (such as: moving the scrollwheel while keeping the cursor over a tab will switch among tabs in applications that use tabs). But even if we accept the annoying use-the-scrollwheel-for-everything-at-all-costs fashion, only two behaviors would make sense in this case: Option A: - similar to current behavior (switch between windows of an application) but ONLY IF there are more than one window of that application open AND one of those window is already focused. Or option B: - whenever the scrollwheel is on the launcher, scrolling would switch among ALL existing windows Both option A and B would be consistent with the widespread scrollwheel abuse, but would at least make sense, and an unintentional movement of the scrollwheel causing an undesired window switching could always be reverted by a countermovement of the scrollwheel in the opposite direction. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Dec 23 22:45:54 2013 InstallationDate: Installed on 2013-10-11 (73 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263786 Title: Nonsense behavior of scrollwheel over Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1263786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263197] [NEW] bluetooth turned off without a reason
Public bug reported: I turned on my computer and the bluetooth icon in the notification area was not present. It usually is. So I launched Bluetooth from the dash, and Bluetooth was turned off. I turned on, so the icon on the notification area appeared. The question is why it got turned off if it used to be always turned on by default ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-bluetooth 0.0.6daily13.02.19-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Fri Dec 20 19:02:08 2013 InstallationDate: Installed on 2013-10-11 (70 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263197 Title: bluetooth turned off without a reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1263197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262309] [NEW] print tray icon disappeared just when clicking it
Public bug reported: I was printing a document, which was taking very long as per bug #1262308 I clicked on the printer tray icon in the notification area. An empty submenu unfolded for a fraction of a second and then immediately the printer icon disappeared, while the printer was still printing (a line every 10 seconds) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cups 1.6.2-1ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CupsErrorLog: W [18/Dec/2013:00:57:25 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'HP_DeskJet_940C-Gray..' already exists W [18/Dec/2013:00:57:25 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'HP_DeskJet_940C-RGB..' already exists Date: Wed Dec 18 19:13:57 2013 InstallationDate: Installed on 2013-10-11 (68 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Lpstat: device for HP_DeskJet_940C: hp:/usb/DeskJet_940C?serial=MY17O671S5BH MachineType: Acer Aspire V3-571G MarkForUpload: True Papersize: a4 PpdFiles: HP_DeskJet_940C: HP Deskjet 940c, hpcups 3.13.3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262309 Title: print tray icon disappeared just when clicking it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1262309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262308] Re: Printing has become super slow. Worked before
And then see https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1262309 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262308 Title: Printing has become super slow. Worked before To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1262308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 968427] Re: pen drive suddenly unmounts and remounts as read-only
OMG, another bug that expires without knowing whether it is fixed. No I haven't tested it on 13.10. Has anybody? If you have tested it and it's fixed then mark it as fixed If you haven't, leave it as either incomplete or confirmed. No reason to close a bug without having checked that it's fixed or having the slightest reason to think it may be fixed (and if you have, then test it before closing it). Bug expiration should be abolished completely. ** Changed in: linux (Ubuntu) Status: Expired = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/968427 Title: pen drive suddenly unmounts and remounts as read-only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/968427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262308] [NEW] Printing has become super slow. Worked before
Public bug reported: I've sent a text document to the printer from GEdit. It has printed it at one line every 10 seconds. It would print a line, then wait like 10 seconds, then print the next line, etc. At the end the file has been printed fine, but this is not a normal speed. Up to yesterday it would print around 4-6 lines per second or so. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cups 1.6.2-1ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CupsErrorLog: W [18/Dec/2013:00:57:25 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'HP_DeskJet_940C-Gray..' already exists W [18/Dec/2013:00:57:25 +0100] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'HP_DeskJet_940C-RGB..' already exists Date: Wed Dec 18 19:12:50 2013 InstallationDate: Installed on 2013-10-11 (68 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Lpstat: device for HP_DeskJet_940C: hp:/usb/DeskJet_940C?serial=MY17O671S5BH MachineType: Acer Aspire V3-571G MarkForUpload: True Papersize: a4 PpdFiles: HP_DeskJet_940C: HP Deskjet 940c, hpcups 3.13.3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262308 Title: Printing has become super slow. Worked before To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1262308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254106] Re: browse files on device does nothing
Please reconsider the reassignment to Nautilus. I don't think the bluetooth widget in the notification area has nothing to do with Nautilus. And when I click on the device listed there, the computer does NOT EVEN TRY TO CONNECT to the phone; I guess it would open Nautilus after establishing a connection to the device, so if it doesn't even try I don't think Nautilus has anything to do here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254106 Title: browse files on device does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1254106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254106] Re: browse files on device does nothing
If I open BlueTooth Settings, then select the device from the list on the left, then click on the Browse Files button, then IT WORKS. It's definitely the notification-area widget that it's broken. I'm going to change this to confirmed because if we wait for someone else to test it (let alone confirm it) we're going to wait forever. There's enough information in this report to start fixing it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254106 Title: browse files on device does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1254106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254106] Re: browse files on device does nothing
(the hcidump itself confirms it) ** Changed in: nautilus (Ubuntu) Status: New = Confirmed ** Package changed: nautilus (Ubuntu) = indicator-bluetooth (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254106 Title: browse files on device does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1254106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262382] [NEW] browsing files on a bluetooth device: doesn't show dates, makes it unusable
Public bug reported: When browsing files on a bluetooth device, the date is not available. If you choose the list mode, the modification date column shows unknown for all files. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Wed Dec 18 21:51:04 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1274x564+395+266' InstallationDate: Installed on 2013-10-11 (68 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262382 Title: browsing files on a bluetooth device: doesn't show dates, makes it unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1262382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261148] [NEW] nautilus became unusably slow to respond. Restarting fixed the issue
Public bug reported: I had a Nautilus window that had been open for hours and had survived more than one suspend/resume of the computer. I used it every once in a while, as I usually do. Then I brought it to front to do some stuff (after maybe a few hours of not using it) and it suddenly was unusably slow in responding to mouse interaction. - When opening any folder (folder with little contents which usually take a fraction of a second to open) it would take up to 10 or 15 seconds to show the contents (during that time it would show an empty window as if the folder was empty, with no indication whatsoever that it was loading or waiting) - When scrolling, either with the touchpad two-fingers scroll or with the scrollbar, it would take several seconds to render the scrolling. I closed and relaunched Nautilus and it fixed the issue. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Sun Dec 15 15:14:35 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1068x506+116+110' InstallationDate: Installed on 2013-10-11 (64 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261148 Title: nautilus became unusably slow to respond. Restarting fixed the issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1261148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261217] Re: screen gets full of small horizontal black segments at random times
To apport's question Is the issue purely graphical? (it will be reported against Compiz I answered yes, so I don't understand why it has been reported against Unity allthesame -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261217 Title: screen gets full of small horizontal black segments at random times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1261217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1261217] [NEW] screen gets full of small horizontal black segments at random times
Public bug reported: Since the last reboot, from time to time, randomly, the screen gets filled of short vertical black lines (segments), for a fraction of a second or few seconds, then gets back to normal. Now a few minutes have passed and apparently it has stopped doing it. Prior to this last reboot some updates had been installed (that's why I had to reboot), and I had never ever seen this happen before, so this may be a regression in some recent update. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12 Uname: Linux 3.8.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Dec 15 21:37:06 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.8.0-32-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-33-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-34-generic, x86_64: installed 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 / 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 (65 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.7-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.7-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sun Dec 15 21:10:19 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6.2 xserver.video_driver: intel ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261217 Title: screen gets full of small horizontal black segments at random times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1261217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1023964] Re: apport-collect has missing dependence: launchpadlib Python
Why is this a wontFix?!?!? If apport-collect depends on a package which is not installed, then when trying to run it, it should give this warning: $ apport-collect You need to run 'sudo apt-get install python-apport' for apport-collect to work. Instead it says: $ apport-collect 1250488 ERROR: The launchpadlib Python module is not installed. This functionality is not available. and you have to figure out what the hell you need to install. That's a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1023964 Title: apport-collect has missing dependence: launchpadlib Python To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1023964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1023964] Re: apport-collect has missing dependence: launchpadlib Python
Actually it's not python-apport, it's already installed. It's something else that is missing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1023964 Title: apport-collect has missing dependence: launchpadlib Python To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1023964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250488] Re: USB hub stopped working on a given USB port (would work on any other port). Reboot fixed the issue
Happened again. Lsusb when the hub is connected to the port where it does not work: $ lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 067: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120 Bus 003 Device 068: ID 0409:005a NEC Corp. HighSpeed Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 033: ID 0489:e04e Foxconn / Hon Hai Bus 001 Device 004: ID 04f2:b374 Chicony Electronics Co., Ltd Bus 003 Device 069: ID 03f0:1604 Hewlett-Packard DeskJet 940c Bus 003 Device 070: ID 0409:005a NEC Corp. HighSpeed Hub Bus 003 Device 071: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09 Lsusb when connected to the port where it DOES work: $ lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 063: ID 0409:005a NEC Corp. HighSpeed Hub Bus 003 Device 062: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 033: ID 0489:e04e Foxconn / Hon Hai Bus 001 Device 004: ID 04f2:b374 Chicony Electronics Co., Ltd Bus 003 Device 064: ID 03f0:1604 Hewlett-Packard DeskJet 940c Bus 003 Device 065: ID 0409:005a NEC Corp. HighSpeed Hub Bus 003 Device 066: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09 Strangely enough, they are almost the same. I can see the printer listed in both, for example, which is connected to the hub; yet, the printer does not work in the first case. Neither does the keyboard, but I don't know which device in the list the keyboard is. @jsalisbury may yo explain why on earth you marked this as incomplete?? ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250488 Title: USB hub stopped working on a given USB port (would work on any other port). Reboot fixed the issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1250488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1259625] [NEW] Whole system stops responding because of a single buggy application
Public bug reported: As per this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=72569 there's a bug in LibreOffice that causes it to stop responding in certain reproducible situations. The relevant thing here is that the WHOLE SYSTEM stops responding and you can't even switch window, open a terminal, or close the offending application, in this case Libre OFfice. If a single buggy (or even malicious) application can cause the whole system to become unusable, there is a bug in the system itself. I can switch to a virtual console with ctrl+alt+f1 and kill the offending libreOffice process in this case, so I guess the issue is somewhere between Unity and X, rather than in linux. But this is only a guess. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Dec 10 17:38:35 2013 InstallationDate: Installed on 2013-10-11 (59 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259625 Title: Whole system stops responding because of a single buggy application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1259625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258802] [NEW] Network Manager crash
Public bug reported: Network manager has suddenly crashed. Hope the information gathered by Approt will help to fix the issue. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Sat Dec 7 18:50:42 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (57 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 metric 9 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258802 Title: Network Manager crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1258802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258802] Re: Network Manager crash
Confirming because it is a crash (crashes shouldn't need an extra confirmation by somebody else) ** Changed in: network-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/1258802 Title: Network Manager crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1258802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1256425] [NEW] whole screen became blank white - no recovery possible - after unplugging and replugging external monitor
Public bug reported: I have a laptop with an external monitor connected. When the monitor is connected, I only use the external monitor. Usually, when I unplug the monitor, the screen switches automatically, i.e. the builtin screen turns on; when I replug the external monitor, the builtin screen turns off an the external monitor turns on. A few minutes ago I unplugged the external monitor, and the builtin screen became all white. I could see the mouse cursor on a white background and nothing else. The mouse cursor moved smoothly, but I could'nt do anything. Keystrokes such as tab, atl+tab, ctrl+alt+T (to open a terminal), Ctrl+Super+D, and the like, did absolutely nothing (or they do what they are supposed to do but I couldn't see it because the screen remained white. Replugging the monitor didn't fix the issue. When I plugged the monitor, the builtin screen would turn off, the external monitor would turn on but I could only see a white rectangle (probably of the same size as the laptop built in screen) on a black background, and the mouse cursor. Switching between virtual terminals (i.e. Ctrl+Alt+F1 and Ctrl+Alt+F7) worked, but wouldn't fix the issue. I had no other option than reboot (which I had to do from the F1 virtual terminal), obviously losing all my unsaved work because of such a stupid bug, when probably all programs were running fine but invisibly. Please tell me what can be done to force a wake up of the screen as a workaround so next time this happens at least I don't have to reboot and lose all my data. I think this is a REGRESSION, or at least I had never, ever seen this before in years of using ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Nov 29 21:46:27 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.2, 3.8.0-32-generic, x86_64: installed vboxhost, 4.3.2, 3.8.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M / 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 (49 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.7-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.7-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Fri Nov 29 21:44:54 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6.2 xserver.video_driver: intel ** Affects: xorg (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug compiz-0.9 raring ubuntu ** 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/1256425 Title: whole screen became blank white - no recovery possible - after unplugging and
[Bug 1256425] Re: whole screen became blank white - no recovery possible - after unplugging and replugging external monitor
Confirming though it's my own report as this is the kind of bug where there's no point in waiting for somebody else to observe it, and it needs urgent attention. Please set the importance to Critical unless there is a workaround, as this renders the whole system unusable and causes 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/1256425 Title: whole screen became blank white - no recovery possible - after unplugging and replugging external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1256425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255670] [NEW] Battery indicator shows an almost empty battery when charging though the battery is almost full
Public bug reported: Right now, if I disconnect the charger from the laptop, the battery indicator shows an almost-empty battery with an electricity symbol - whose meaning can only be that the battery is almost empty and is being charged. If I disconnect the charger, then the icon shows a completely full battery (without the electricity symbol). Which can only mean that the battery is practically full. So the information displayed is contraddictory. The former is wrong, and the latter is right. The battery is actually almost full. If I click on the icon when charging (connected), it says 0:13 to charge. If I click on it when disconnected, it says 3:45 left. These are consistent with each other, and with the fact that the battery actually _is_ almost full. The battery is almost new and it takes pretty long to discharge, so it can't be almost full and almost empty at the same time, nor is the measured value unreliable. The fact that the textual information is correct confirms this. It's a bug in the way the information is displayed graphically. Actually, while I was writing, the charging completed, the battery is now full. If I click on the icon, it says Battery (100%). However, the icon still shows the almost empty battery. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-33-generic 3.8.0-33.48 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2017 F pulseaudio Date: Wed Nov 27 21:21:12 2013 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (47 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-33-generic N/A linux-backports-modules-3.8.0-33-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255670 Title: Battery indicator shows an almost empty battery when charging though the battery is almost full To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255679] [NEW] Battery status should show percentage as well as (or rather than) time or allow you to choose
Public bug reported: When you click on the battery icon (or if you have checked the show time in menu bar option) It's great that the battery indicator tells you how much *time* is needed to finish charging the battery (when charging), or how much time is left (when discharging), even though we all know this estimate is far from reliable. However, this cannot come at the price of not knowing the *percentage* of charge. Given its intrinsic unreliability, the time information is almost useless in most cases. The percentage MUST be shown. Three behaviors would be acceptable: - only show percentage - show both percentage and time - let me choose But showing only time is definitely wrong. Additionally, to add more confusion and frustration, the indicator exhibits the following twisted behavior: When you click on the icon: - Connected and charging = x:xx to charge - Connected and fully charged = sometimes 100%, sometimes charged - Disconnected = y:yy left When you have already clicked on it and the submenu is already visible, and you connect or disconnect the charger, then value is updated in the following way, and then after a few seconds it changes to the behavior described above: - Just connected and fully charged = charged (then it may change to 100%, or not) - Just connected and charging = nn% (then it changes to x:xx to charge) - Just disconnected = nn% (then it changes to y:yy left) When the show time in Menu Bar option is checked, the behavior is the same as described above (including the changes when connecting/disconnecting) with the slight difference that instead of charged nothing is shown. Actually I suspect the difference between 100% and charged above is not random but maybe 100% means more than 99.5% but still detectably less than 100%, while charged means not distinguishable from 100% as far as the sensor can tell. If that is the case, this distinction is not significant to the user and this way of conveying it is confusing. It would be more fair to either show 99% whenever the battery is detectably non-full (even if it is greater than 99.5%) or to always show either 100% or charged (but always the same) when the amount of charge rounds up to 100%. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-33-generic 3.8.0-33.48 ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo2017 F pulseaudio Date: Wed Nov 27 21:42:15 2013 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (47 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Acer Aspire V3-571G MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-33-generic N/A linux-backports-modules-3.8.0-33-generic N/A linux-firmware1.106 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255679 Title: Battery status should show percentage as well as (or rather than) time or allow you to choose To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254106] [NEW] browse files on device does nothing
Public bug reported: I click on the Bluetooth icon on the top-right corner of the screen next to the battery icon My mobile phone is listed in the drop down. I select it and I click on Browse files Expected: a Nautilus window should appear showing the browsable contents of the device. Maybe the device should prompt me whether to allow browsing before Observed: ABSOLUTELY NOTHING happens. The computer doesn't even try to connect to the phone. Nothing happens on the phone, nothing happens on the computer; no error message is shown anywhere, it's just as if I had done nothing. I've done an hcidump while trying this, and it's empty. This HAD WORKED BEFORE on the same machine and with the same device. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.8.0-33.48-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 Date: Fri Nov 22 17:53:08 2013 InstallationDate: Installed on 2013-10-11 (41 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire V3-571G MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-33-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer 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:549 acl:0 sco:0 events:31 errors:0 TX bytes:1168 acl:0 sco:0 commands:31 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254106 Title: browse files on device does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1254106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254106] Re: browse files on device does nothing
Actually I think the issue is in the widget or applet or whatever it's called that appears in the notification area. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254106 Title: browse files on device does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1254106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250407] Re: printer has stopped working. Filter failed
I fixed the issue by running hp-setup. It discovered the printer, created a new instance of the printer, I deleted the old one, and the new one works. Anyway it's ridiculous that an existing printer just breaks. I'll confirm the bug as I think there's enough information in the report to address it, and there's no point in waiting for somebody else to stumble on the same issue _and_ on the bug report. ** Changed in: cups (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/1250407 Title: printer has stopped working. Filter failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1250407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
