[Bug 1661486] Re: nouveau write fault, CTXSW_TIMEOUT, hangs the display
I switched from nouveau to the proprietary nvidia driver (nvidia-375), and the crashes have stopped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661486 Title: nouveau write fault, CTXSW_TIMEOUT, hangs the display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1661486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658185] Re: nouveau occasionally won't come back from DPMS suspend/off
David, by any chance, are you running VMware Workstation when these problems happen? My computer has similar symptoms, and when I ssh in, VMware Workstation seems to be in an odd state. I can't suspend my VMs from the command line (in preparation for a reboot of the host). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658185 Title: nouveau occasionally won't come back from DPMS suspend/off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1658185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661486] Re: nouveau write fault, CTXSW_TIMEOUT, hangs the display
This crash is now happening daily, ever since the latest plasma upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661486 Title: nouveau write fault, CTXSW_TIMEOUT, hangs the display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1661486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661486] [NEW] nouveau write fault, CTXSW_TIMEOUT, hangs the display
Public bug reported: A few hours after upgrading to the latest kernel and plasma (using apt upgrade) in Xenial 16.04LTS, my computer display hung with: Feb 2 20:36:16 snorkack kernel: [83600.290217] nouveau :01:00.0: fifo: write fault at 27c000 engine 00 [GR] client 0e [GPC0/GPCCS] reason 02 [PTE] on channel 2 [007f9a3000 Xorg[1501]] Feb 2 20:36:16 snorkack kernel: [83600.290221] nouveau :01:00.0: fifo: gr engine fault on channel 2, recovering... Feb 2 20:33:42 snorkack colord[1394]: (colord:1394): Cd-WARNING **: failed to get session [pid 27934]: No such device or address Feb 2 20:36:19 snorkack vmnet-dhcpd: DHCPREQUEST for 192.168.50.128 from 00:0c:29:d5:2d:15 via vmnet8 Feb 2 20:36:19 snorkack vmnet-dhcpd: DHCPACK on 192.168.50.128 to 00:0c:29:d5:2d:15 via vmnet8 Feb 2 20:36:20 snorkack kernel: [83604.585547] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:20 snorkack kernel: [83604.585553] nouveau :01:00.0: fifo: sw engine fault on channel 8, recovering... Feb 2 20:36:22 snorkack kernel: [83606.583732] nouveau :01:00.0: fifo: runlist 0 update timeout Feb 2 20:36:24 snorkack kernel: [83608.880576] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:29 snorkack kernel: [83613.175601] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:33 snorkack kernel: [83617.470624] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:37 snorkack kernel: [83621.765648] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 2 20:36:42 snorkack kernel: [83626.060672] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] ...repeats many times... I could still log in via SSH but could not unhang the system, so I rebooted. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-nouveau 1:1.0.12-1build2 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: KDE Date: Thu Feb 2 23:20:22 2017 InstallationDate: Installed on 2016-09-25 (131 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661486 Title: nouveau write fault, CTXSW_TIMEOUT, hangs the display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1661486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628707] Re: Highlighting a region in emacs is invisible because region color equals window color
It's possible that some X resource hidden in my account is setting the background color. Can someone please tell me where to look for these resource settings? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628707 Title: Highlighting a region in emacs is invisible because region color equals window color To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1628707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628707] [NEW] Highlighting a region in emacs is invisible because region color equals window color
Public bug reported: If you open an Emacs window in Plasma/KDE, and you try to highlight a region of text by dragging the mouse, no highlighting appears. This is because the color for highlighting a region is identical to the color for the window background. I believe this color clash occurs between Ubuntu's emacs24 package and Ubuntu's X resource settings. To reproduce, log into Plasma, remove your $HOME/.emacs init file (so you have no personal customizations), and run emacs in an X window: $ emacs The window's background color is a light gray. Then type any text, click and drag the mouse over the text (or use keystroke commands to define a region). No highlighting appears, because the "region" color is also light gray. You can see this by running the emacs command: M-x list-faces-display I'll attach a screenshot so you can see that the "region" highlighting doesn't show up. The problem goes away if you disable the Ubuntu-supplied emacs init files: $ emacs -Q This is why I suspect the color is set badly in the Ubuntu emacs24 package. You can see the X background color by running the "appres" command in a shell window, which proves a light gray background is set, the same color as region highlighting: *background:#eff0f1 I tried to find the file where this background color is set, but I was not successful. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: emacs24 24.5+1-6ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Wed Sep 28 18:07:25 2016 InstallationDate: Installed on 2016-09-25 (3 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: emacs24 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: emacs24 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "The "region" face shows no highlighting" https://bugs.launchpad.net/bugs/1628707/+attachment/4750558/+files/region.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628707 Title: Highlighting a region in emacs is invisible because region color equals window color To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs24/+bug/1628707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610574] Re: mysql_secure_installation locks out root database user
>After running secure_installation, can you still log in with «sudo >mysql» with no password or user specified? I succeeded with "sudo mysql -u root". I did not try it with no user specified. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610574 Title: mysql_secure_installation locks out root database user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1610574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610574] Re: mysql_secure_installation locks out root database user
FYI, if you have any difficulty reproducing this issue, I actually installed the mysql-server package using Puppet (version 3.8.5), not manually with apt-get. The puppet manifest file contains simply: package { 'mysql-server': ensure => 'installed', } To run it, simply place the above lines into a file (say) "build.pp" and run this puppet command: $ sudo puppet apply build.pp I suspect this may be relevant. ** Description changed: Install the 16.04 package mysql-server and immediately run mysql_secure_installation to set the root database password. When complete, the root database password you chose doesn't work. You are locked out from mysql. - Steps reproduce on a fresh Xenial system: + Steps to reproduce this issue on a fresh Xenial system: 1. sudo apt-get install mysql-server 2. sudo mysql_secure_installation 3. Respond to the questions: - Validate password plugin? No - New password: foobarblat - Re-enter new password: foobarblat - Remove anonymous users? Y - Disallow root login remotely? Y - Remove test database and access to it? Y - Reload privilege tables now? Y 4. mysql -p -u root Enter password: foobarblat ERROR 1698 (28000): Access denied for user 'root'@'localhost' Other people have encountered the same problem: http://askubuntu.com/questions/766334/cant-login-as-mysql-user-root-from-normal-user-account-in-ubuntu-16-04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610574 Title: mysql_secure_installation locks out root database user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1610574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610574] [NEW] mysql_secure_installation locks out root database user
Public bug reported: Install the 16.04 package mysql-server and immediately run mysql_secure_installation to set the root database password. When complete, the root database password you chose doesn't work. You are locked out from mysql. Steps reproduce on a fresh Xenial system: 1. sudo apt-get install mysql-server 2. sudo mysql_secure_installation 3. Respond to the questions: - Validate password plugin? No - New password: foobarblat - Re-enter new password: foobarblat - Remove anonymous users? Y - Disallow root login remotely? Y - Remove test database and access to it? Y - Reload privilege tables now? Y 4. mysql -p -u root Enter password: foobarblat ERROR 1698 (28000): Access denied for user 'root'@'localhost' Other people have encountered the same problem: http://askubuntu.com/questions/766334/cant-login-as-mysql-user-root-from-normal-user-account-in-ubuntu-16-04 ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610574 Title: mysql_secure_installation locks out root database user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1610574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581077] [NEW] Ubuntu asks to upgrade during an upgrade
Public bug reported: I was in the middle of an upgrade from Vivid to Wily. "sudo do-release- upgrade" was running on the system console. Suddenly, a dialog popped up, saying there's a new version of Ubuntu available, and do I want to upgrade? This dialog was confusing; I didn't know if it was part of the upgrade currently in progress, or some other upgrade. If I had clicked the "Upgrade" button, perhaps it would have launched a Xenial upgrade while the Wily upgrade was still running. I suggest that this dialog should be suppressed if an upgrade is currently in progress. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581077 Title: Ubuntu asks to upgrade during an upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1581077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1517030] Re: ubuntu-bug (apport-kde) crashes every time I submit a problem report
Someone has just posted a one-line fix, so is it possible for this fix to be incorporated? ** Changed in: apport (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1517030 Title: ubuntu-bug (apport-kde) crashes every time I submit a problem report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1517030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219529] Re: df -x tmpfs fails to exclude udev (/dev)
This bug still exists in 15.10 - confirming. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1219529 Title: df -x tmpfs fails to exclude udev (/dev) To manage notifications about this bug go to: https://bugs.launchpad.net/coreutils/+bug/1219529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1517030] Re: ubuntu-bug (apport-kde) crashes every time I submit a problem report
Hi - I uploaded the requested crash file. Should the "incomplete" status be changed? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1517030 Title: ubuntu-bug (apport-kde) crashes every time I submit a problem report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1517030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1223291] Re: "sudo emacs" cannot be backgrounded afterward by shell
This appears to be fixed as of Ubuntu 15.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1223291 Title: "sudo emacs" cannot be backgrounded afterward by shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/1223291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1223291] Re: "sudo emacs" cannot be backgrounded afterward by shell
I would close this if I could. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1223291 Title: "sudo emacs" cannot be backgrounded afterward by shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/1223291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1523143] [NEW] kalarm writes "Check" lines to ~/.xsession-errors every minute
Public bug reported: kalarm is writing continually to $HOME/.xsession-errors. This kind of pointless logging will silently fill the /home partition. The lines are: log_kalarm: log_kalarm: log_koalarmclient: Check: "Fri Dec 4 17:00:43 2015" - "Fri Dec 4 17:01:42 2015" log_kalarm: log_kalarm: log_koalarmclient: Check: "Fri Dec 4 17:01:43 2015" - "Fri Dec 4 17:02:42 2015" log_kalarm: log_kalarm: log_koalarmclient: Check: "Fri Dec 4 17:02:43 2015" - "Fri Dec 4 17:03:42 2015" log_kalarm: log_kalarm: log_koalarmclient: Check: "Fri Dec 4 17:03:43 2015" - "Fri Dec 4 17:04:42 2015" log_kalarm: log_kalarm: log_koalarmclient: Check: "Fri Dec 4 17:04:43 2015" - "Fri Dec 4 17:05:42 2015" etc. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: kalarm 4:15.08.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: KDE Date: Sat Dec 5 12:46:11 2015 InstallationDate: Installed on 2013-08-31 (825 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: kdepim UpgradeStatus: Upgraded to wily on 2015-11-08 (26 days ago) ** Affects: kdepim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523143 Title: kalarm writes "Check" lines to ~/.xsession-errors every minute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/1523143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515829] Re: Gimp tooltip text color is white on white
Thank you, antonio -- your workaround in comment #3 fixed the problem for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515829 Title: Gimp tooltip text color is white on white To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1515829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 890913] Re: Typing "prg $HOME/" expands to "prg \$HOME/"
This bug used to affect me in 14.04 LTS. Since upgrading to 15.10, the bug no longer occurs for me. Just another data point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/890913 Title: Typing "prg $HOME/" expands to "prg \$HOME/" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/890913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1517030] Re: ubuntu-bug (apport-kde) crashes every time I submit a problem report
Here's the crash file you requested ** Attachment added: "The requested crash file" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1517030/+attachment/4521620/+files/_usr_share_apport_apport-kde.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1517030 Title: ubuntu-bug (apport-kde) crashes every time I submit a problem report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1517030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1517030] [NEW] ubuntu-bug (apport-kde) crashes every time I submit a problem report
Public bug reported: Every time I run the "ubuntu-bug" program, I get a crash report about it. 1. I run (say) "ubuntu-bug muon-updater" 2. Apport window appears, "Send problem report to developers?" with info about the bug. 3. Click Send. 4. "Uploading problem information" dialog appears and disappears. 5. Launchpad website appears. I start filing in details. 6. Sometime soon, Plasma reports a crash in its system tray. A dialog appears. See my screenshot. 7. I click the "Continue" button to submit a crash bug report. The dialog disappears, but nothing else happens that I can see. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport-kde 2.19.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 17 07:51:26 2015 InstallationDate: Installed on 2013-08-31 (807 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to wily on 2015-11-08 (8 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Attachment added: "Dialog that appears after apport-kde crash" https://bugs.launchpad.net/bugs/1517030/+attachment/4520579/+files/dialog.png ** Summary changed: - ubuntu-bug crashes every time I submit a problem report + ubuntu-bug (apport-kde) crashes every time I submit a problem report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1517030 Title: ubuntu-bug (apport-kde) crashes every time I submit a problem report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1517030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1517030] Re: ubuntu-bug (apport-kde) crashes every time I submit a problem report
Also, when ubuntu-bug terminates, the shell prints: Segmentation fault (core dumped) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1517030 Title: ubuntu-bug (apport-kde) crashes every time I submit a problem report To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1517030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1517027] [NEW] System tray icon for Updates appears with red X when software is already up to date
Public bug reported: *After* I do a software update from the command line: $ sudo apt-get upgrade a new icon appears in my system tray, which looks like a shield with a red "X" on it. (See screenshot.) To my eye, the red X means that my software is out of date. However, my software is up to date. This behavior seems backwards. Shouldn't the icon appear *before* the update, and then disappear after the update? When I click the icon, a rectangle appears that says "Updates: System up to date." There appears to be no way to make this icon disappear, short of hiding it permanently. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: muon-updater 4:5.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 17 07:43:49 2015 InstallationDate: Installed on 2013-08-31 (807 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: muon UpgradeStatus: Upgraded to wily on 2015-11-08 (8 days ago) ** Affects: muon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Attachment added: "System tray AFTER a software update" https://bugs.launchpad.net/bugs/1517027/+attachment/4520575/+files/tray.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1517027 Title: System tray icon for Updates appears with red X when software is already up to date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/muon/+bug/1517027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515829] [NEW] Gimp tooltip text color is white on white
Public bug reported: In the gimp toolbox, when I hover my mouse over a tool, the tooltip that pops up has white text on a white background. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gimp 2.8.14-1ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 20:18:16 2015 InstallationDate: Installed on 2013-08-31 (803 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gimp UpgradeStatus: Upgraded to wily on 2015-11-08 (4 days ago) ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Attachment added: "Demonstrating the text color problem" https://bugs.launchpad.net/bugs/1515829/+attachment/4517907/+files/bug2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515829 Title: Gimp tooltip text color is white on white To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1515829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514279] [NEW] User Manager hangs after selecting a photo
Public bug reported: 1. Run "System Settings" 2. Choose "Account Settings", then "User Manager" 3. Select my own account. 4. Click the icon to choose a photograph and select "Load from file..." 5. Navigate to a JPEG file and select it. Click "Open". My photograph appears in place of the icon. 6. In User Manager, click "Apply". 7. System Settings hangs. I reproduced this 5 times in a row. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: systemsettings 4:5.4.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3 Uname: Linux 4.2.0-17-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Nov 8 20:29:06 2015 InstallationDate: Installed on 2013-08-31 (799 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: systemsettings UpgradeStatus: Upgraded to wily on 2015-11-08 (0 days ago) ** Affects: systemsettings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1514279 Title: User Manager hangs after selecting a photo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1514279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1477801] Re: libdrm-nouveau2 crashes X with kernel 3.13.0-58
Thank you Peter!!! I am not familiar with the migration path from a PPA to the official Ubuntu release. Is your fix likely to become part of official 14.04.1 LTS, and if so, how long does that usually take? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1477801 Title: libdrm-nouveau2 crashes X with kernel 3.13.0-58 To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1477801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1477801] Re: libdrm-nouveau2 crashes X with kernel 3.13.0-58
Thank you Peter. Do you know if the 2.4.61 fix can be applied to Ubuntu 14.04 LTS officially? This is one deadly bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1477801 Title: libdrm-nouveau2 crashes X with kernel 3.13.0-58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1477801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1477801] [NEW] libdrm-nouveau2 crashes X with kernel 3.13.0-58
Public bug reported: (Apologies for not using ubuntu-bug, but I've been waiting an hour for it to get past "Collecting problem information".) I upgraded system to kernel 3.16.0-43.58~14.04.1 (amd64) today. X now crashes with the error "nouveau - gpu lockup" whenever I run Google Chrome (google-chrome-stable 44.0.2403.89-1). Big black boxes appear when I open a bunch of tabs and hover the mouse over the tabs. Eventually X crashes, freezing the whole screen with garbage all over it, and syslog contains the "nouveau" errors below. The problem went away when I downgraded libdrm2 and libdrm-nouveau2 to 2.4.56-1~ubuntu2 (was 2.4.60-2~ubuntu14.04.1). I did this after reading https://bugs.freedesktop.org/show_bug.cgi?id=89842#c19 (see comment #19). Here's syslog. The "nouveau gpu lockup" error doesn't appear, but it did appear onscreen. Jul 23 19:22:35 myhost kernel: [ 2568.498288] nouveau E[chrome[7073]] multiple instances of buffer 322 on validation list Jul 23 19:22:35 myhost kernel: [ 2568.498297] nouveau E[chrome[7073]] validate_init Jul 23 19:22:35 myhost kernel: [ 2568.498299] nouveau E[chrome[7073]] validate: -22 Jul 23 19:22:35 myhost kernel: [ 2568.514019] nouveau E[ PFIFO][:01:00.0] PFIFO: read fault at 0x0008101000 [PAGE_NOT_PRESENT] from (unknown enum 0x)/GPC0/(unknown enum 0x000f) on channel 0x007f9af000 [unknown] Jul 23 19:23:06 myhost kernel: [ 2598.744949] nouveau E[ DRM] GPU lockup - switching to software fbcon Jul 23 19:23:23 myhost kernel: [ 2616.347931] nouveau E[Xorg[1550]] failed to idle channel 0x0001 [Xorg[1550]] Jul 23 19:23:38 myhost kernel: [ 2631.335533] nouveau E[Xorg[1550]] failed to idle channel 0x0001 [Xorg[1550]] Jul 23 19:23:40 myhost kernel: [ 2633.336751] nouveau E[ PFIFO][:01:00.0] playlist 0 update timeout Jul 23 19:23:43 myhost kernel: [ 2635.629793] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:23:47 myhost kernel: [ 2639.921155] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:23:50 myhost vmnet-dhcpd: DHCPINFORM for 192.168.142.131 from 00:0c:29:d5:2d:15 via vmnet8 Jul 23 19:23:50 myhost vmnet-dhcpd: DHCPACK on 192.168.142.131 to 00:0c:29:d5:2d:15 via vmnet8 Jul 23 19:23:51 myhost kernel: [ 2644.212519] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:23:55 myhost kernel: [ 2648.321472] nouveau E[Xorg[1550]] failed to idle channel 0x [Xorg[1550]] Jul 23 19:23:56 myhost kernel: [ 2648.503871] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:24:00 myhost kernel: [ 2652.795221] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:24:04 myhost kernel: [ 2657.086572] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:24:08 myhost kernel: [ 2661.377922] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:24:10 myhost kernel: [ 2663.309074] nouveau E[Xorg[1550]] failed to idle channel 0x [Xorg[1550]] Jul 23 19:24:12 myhost kernel: [ 2665.310067] nouveau E[ PFIFO][:01:00.0] playlist 0 update timeout Jul 23 19:24:12 myhost colord: Automatic remove of icc-ed0e29bb4d99e8caee0ed705188568cc from xrandr-Dell Inc.-DELL 2405FPW-T61335980T0S Jul 23 19:24:12 myhost colord: Profile removed: icc-ed0e29bb4d99e8caee0ed705188568cc Jul 23 19:24:12 myhost colord: Profile removed: icc-cc453361e0e5fe47e15ec698dbee0254 Jul 23 19:24:12 myhost colord: device removed: xrandr-Dell Inc.-DELL 2405FPW-T61335980T0S Jul 23 19:24:13 myhost kernel: [ 2665.669272] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:24:17 myhost kernel: [ 2669.960633] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:24:21 myhost kernel: [ 2674.252007] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:24:26 myhost kernel: [ 2678.543381] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:24:27 myhost kernel: [ 2680.434907] nouveau E[chrome[7073]] failed to idle channel 0x [chrome[7073]] Jul 23 19:24:30 myhost kernel: [ 2682.834756] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:24:34 myhost kernel: [ 2687.126132] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:24:38 myhost kernel: [ 2691.417509] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:24:42 myhost kernel: [ 2695.422508] nouveau E[chrome[7073]] failed to idle channel 0x [chrome[7073]] Jul 23 19:24:43 myhost kernel: [ 2695.708885] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:24:44 myhost kernel: [ 2697.420975] nouveau E[ PFIFO][:01:00.0] channel 4 [chrome[7073]] kick timeout Jul 23 19:24:44 myhost kernel: [ 2697.423943] nouveau W[ PFIFO][:01:00.0] unknown status 0x0100 Jul 23 19:24:46 myhost kernel: [ 2699.49] nouveau E[ PFIFO][:01:00.0] playlist 0 update timeout Jul 23 19:24:46 myhost kernel: [ 2699.422279] nouveau ![ PFIFO][
[Bug 1245303] Re: gphoto2 fails to recognize current Canon S100 with An error occurred in the io-library ('Bad parameters')
It definitely works for me on Ubuntu 14.04.2 LTS, with my Canon S100. Previously, it didn't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1245303 Title: gphoto2 fails to recognize current Canon S100 with An error occurred in the io-library ('Bad parameters') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gphoto2/+bug/1245303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404967/+files/UdevLog.txt ** 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/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404966/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] Re: removing kernels should not require a restart afterward
apport information ** Tags added: apport-collected ** Description changed: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) + --- + ApportVersion: 2.14.1-0ubuntu3.11 + Architecture: amd64 + CurrentDesktop: KDE + DistroRelease: Ubuntu 14.04 + HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 + InstallationDate: Installed on 2013-08-31 (632 days ago) + InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcFB: 0 nouveaufb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 + RelatedPackageVersions: + linux-restricted-modules-3.13.0-53-generic N/A + linux-backports-modules-3.13.0-53-generic N/A + linux-firmware 1.127.12 + RfKill: + + Tags: trusty + Uname: Linux 3.13.0-53-generic x86_64 + UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) + UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 08/12/2013 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 4210 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: P9X79 + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.name: System Product Name + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404953/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404963/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404960/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404956/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404964/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404957/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404962/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404958/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404965/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404955/+files/BootDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404954/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404961/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1458204/+attachment/4404959/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1458204] [NEW] apt-get autoremove should not require a restart afterward
Public bug reported: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: apt-get autoremove should not require a restart afterward To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1458204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 627008] Re: Cannot read cd: sound-juicer and gvfs problem (workaround included)
The solution from comment #10 worked for me in 13.10. $ gvfs-mount cdda://sr0 I ran it while the CD was in the drive and sound-juicer was not running. Then I ran sound-juicer and it found the disc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/627008 Title: Cannot read cd: sound-juicer and gvfs problem (workaround included) To manage notifications about this bug go to: https://bugs.launchpad.net/sound-juicer/+bug/627008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248341] Re: gphoto2 cannot detect camera after 13.10 upgrade
*** This bug is a duplicate of bug 1245303 *** https://bugs.launchpad.net/bugs/1245303 Looks like this is a duplicate of 1245303. ** This bug has been marked a duplicate of bug 1245303 gphoto2 fails to recognize current Canon S100 with An error occurred in the io-library ('Bad parameters') -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248341 Title: gphoto2 cannot detect camera after 13.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gphoto2/+bug/1248341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248341] Re: gphoto2 cannot detect camera after 13.10 upgrade
OK, I got my camera recognized by using a different USB port. (My USB switcher was having a problem.) Now gphoto2 says: $ gphoto2 -P *** Error *** An error occurred in the io-library ('Bad parameters'): No error description available *** Error (-110: 'I/O in progress') *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248341 Title: gphoto2 cannot detect camera after 13.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gphoto2/+bug/1248341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248341] Re: gphoto2 cannot detect camera after 13.10 upgrade
"sudo lsusb" does not show the camera either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248341 Title: gphoto2 cannot detect camera after 13.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gphoto2/+bug/1248341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248341] [NEW] gphoto2 cannot detect camera after 13.10 upgrade
Public bug reported: I just upgraded from ubuntu 13.04 to 13.10. gphoto2 can no longer detect my Canon S100 camera. I plug it in via USB, and no messages at all appear in /var/log. $ gphoto2 --list-ports | grep usb usb:002,003 Universal Serial Bus usb:001,003 Universal Serial Bus usbdiskdirect:/dev/sdc USB Mass Storage direct IO usbscsi:/dev/sg4 USB Mass Storage raw SCSI $ gphoto2 --auto-detect Model Port -- $ gphoto2 --debug -P (output is attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gphoto2 2.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 5 17:25:14 2013 InstallationDate: Installed on 2013-08-31 (66 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: gphoto2 UpgradeStatus: Upgraded to saucy on 2013-11-02 (3 days ago) ** Affects: gphoto2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: "output of gphoto2 --debug -P" https://bugs.launchpad.net/bugs/1248341/+attachment/3901023/+files/gphoto2-out.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248341 Title: gphoto2 cannot detect camera after 13.10 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gphoto2/+bug/1248341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1223291] Re: "sudo emacs" cannot be backgrounded afterward by shell
Confirming that this is still broken in Saucy Salamander. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1223291 Title: "sudo emacs" cannot be backgrounded afterward by shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/1223291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221503] Re: completion with ubuntu-bug complains about missing release-upgrade.py
Confirming that this is still broken in Saucy Salamander. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221503 Title: completion with ubuntu-bug complains about missing release-upgrade.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1221503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1224207] Re: bash completion for "sudo svn" prints an infinite loop of comopt error messages
This is still broken in Saucy Salamander. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1224207 Title: bash completion for "sudo svn" prints an infinite loop of comopt error messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1224207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221502] Re: bash completion escapes the dollar sign preceding a variable when it shouldn't
Confirming that this is still broken in Saucy Salamander. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1221502 Title: bash completion escapes the dollar sign preceding a variable when it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1221502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1224207] [NEW] bash completion for "sudo svn" prints an infinite loop of comopt error messages
Public bug reported: Type in a shell (but do not hit Enter): $ sudo svn x Now hit the Tab key, and you get stream of error messages: bash: compopt: -o: option requires an argument compopt: usage: compopt [-o|+o option] [-DE] [name ...] bash: compopt: -o: option requires an argument compopt: usage: compopt [-o|+o option] [-DE] [name ...] bash: compopt: -o: option requires an argument compopt: usage: compopt [-o|+o option] [-DE] [name ...] bash: compopt: -o: option requires an argument compopt: usage: compopt [-o|+o option] [-DE] [name ...] bash: compopt: -o: option requires an argument compopt: usage: compopt [-o|+o option] [-DE] [name ...] bash: compopt: -o: option requires an argument compopt: usage: compopt [-o|+o option] [-DE] [name ...] bash: compopt: -o: option requires an argument compopt: usage: compopt [-o|+o option] [-DE] [name ...] ... ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: bash-completion 1:2.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Wed Sep 11 20:40:09 2013 InstallationDate: Installed on 2013-08-31 (11 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash-completion (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/1224207 Title: bash completion for "sudo svn" prints an infinite loop of comopt error messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1224207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222179] Re: /usr/bin/mail has no package
Thanks very much for considering my report. I have marked it as invalid. ** Changed in: bsd-mailx (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222179 Title: /usr/bin/mail has no package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1222179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1223291] Re: "sudo emacs" cannot be backgrounded afterward by shell
Sorry, I made a typo in my report. The command: $ sudo emacs gnome-terminal should be: $ sudo gnome-terminal ** Description changed: When I run: - $ sudo emacs /etc/myfile + $ sudo emacs /etc/myfile and later try to background it by typing ^Z in the invoking shell, the keystroke is ignored and merely echoes to the screen as "^Z". This did NOT happen in Ubuntu 10.04 LTS. This does NOT happen for any of the following commands: - $ sudo emacs -nw /etc/myfile(which runs emacs in the existing gnome-terminal window) - $ sudo emacs gnome-terminal (a different program that also opens a window) + $ sudo emacs -nw /etc/myfile (which runs emacs in the existing gnome-terminal window) + $ sudo gnome-terminal (a different program that also opens a window) I realize that there are workarounds, like manually sending the suspend signal: - $ sudo kill -TSTP + $ sudo kill -TSTP but something special and new (and unwanted) is happening with emacs here. Other users have experienced this problem on other distros: http://unix.stackexchange.com/questions/81482/how-to-send-to-background-a-running-process-started-with-sudo ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: emacs23 23.4+1-4ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 10 06:57:04 2013 InstallationDate: Installed on 2013-08-31 (9 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: emacs23 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/1223291 Title: "sudo emacs" cannot be backgrounded afterward by shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/1223291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1223291] [NEW] "sudo emacs" cannot be backgrounded afterward by shell
Public bug reported: When I run: $ sudo emacs /etc/myfile and later try to background it by typing ^Z in the invoking shell, the keystroke is ignored and merely echoes to the screen as "^Z". This did NOT happen in Ubuntu 10.04 LTS. This does NOT happen for any of the following commands: $ sudo emacs -nw /etc/myfile (which runs emacs in the existing gnome-terminal window) $ sudo gnome-terminal (a different program that also opens a window) I realize that there are workarounds, like manually sending the suspend signal: $ sudo kill -TSTP but something special and new (and unwanted) is happening with emacs here. Other users have experienced this problem on other distros: http://unix.stackexchange.com/questions/81482/how-to-send-to-background-a-running-process-started-with-sudo ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: emacs23 23.4+1-4ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Sep 10 06:57:04 2013 InstallationDate: Installed on 2013-08-31 (9 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: emacs23 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: emacs23 (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/1223291 Title: "sudo emacs" cannot be backgrounded afterward by shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/1223291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222639] Re: libsvn-web-perl does not install svnweb-server and templates
Also no templates are installed. Possibly /usr/bin/svnweb-install seems broken too. It creates only a config.yaml file but no templates subdirectory, which contradicts the docs at http://manpages.ubuntu.com/manpages/lucid/man3/SVN::Web.3pm.html#contenttoc3 : "SVN::Web’s output is entirely template driven. SVN::Web ships with a number of different template styles, installed in to the templates/ subdirectory of wherever you ran "svnweb-install"." ** Summary changed: - libsvn-web-perl does not install svnweb-server + libsvn-web-perl does not install svnweb-server and templates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222639 Title: libsvn-web-perl does not install svnweb-server and templates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsvn-web-perl/+bug/1222639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222639] Re: libsvn-web-perl does not install svnweb-server
"apt-file list libsvn-web-perl" does not list svnweb-server among its files. "apt-file search svnweb-server" returns no results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222639 Title: libsvn-web-perl does not install svnweb-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsvn-web-perl/+bug/1222639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222639] [NEW] libsvn-web-perl does not install svnweb-server
Public bug reported: I installed libsvn-web-perl: $ sudo apt-get install libsvn-web-perl and tried running svnweb-server: $ svnweb-server The program 'svnweb-server' is currently not installed. You can install it by typing: sudo apt-get install libsvn-web-perl Notice that the error message is telling me to install the same package I just installed. Running "sudo apt-get install libsvn-web-perl" a second time doesn't help -- just says that the package is already installed. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libsvn-web-perl 0.63-1ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Mon Sep 9 00:05:02 2013 InstallationDate: Installed on 2013-08-31 (8 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: libsvn-web-perl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libsvn-web-perl (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/1222639 Title: libsvn-web-perl does not install svnweb-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsvn-web-perl/+bug/1222639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222181] Re: /usr/bin/mail ignores aliases in $HOME/.mailrc
I am leaving the bug report in place in case this is still a bug in mailutils. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222181 Title: /usr/bin/mail ignores aliases in $HOME/.mailrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailutils/+bug/1222181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222181] Re: /usr/bin/mail ignores aliases in $HOME/.mailrc
OK, I have figured out a workaround with the help of askubuntu.com: http://askubuntu.com/questions/342607/why-does-usr-bin-mail-ignore- aliases-in-home-mailrc Ubuntu installs the "mailutils" package by default, which (inexplicably) does not support $HOME/.mailrc aliases. The alternative package "bsd-mailx" does support .mailrc properly. Installing this package makes everything work. sudo apt-get install bsd-mailx This replaces /usr/bin/mail (and /usr/bin/mailx) with their bsd-mailx implementations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222181 Title: /usr/bin/mail ignores aliases in $HOME/.mailrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailutils/+bug/1222181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222181] Re: /usr/bin/mail ignores aliases in $HOME/.mailrc
After some investigation, it seems /usr/bin/mail is part of the mailutils package. So this alias expansion should be happening within /usr/bin/mail and not from postfix. ** Package changed: postfix (Ubuntu) => mailutils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222181 Title: /usr/bin/mail ignores aliases in $HOME/.mailrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mailutils/+bug/1222181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222179] Re: /usr/bin/mail has no package
Ah, I notice that /usr/bin/mail is a symlink: $ ll /usr/bin/mail lrwxrwxrwx 1 root root 22 Aug 31 16:55 /usr/bin/mail -> /etc/alternatives/mail and its target is also a symlink: $ ll /etc/alternatives/mail lrwxrwxrwx 1 root root 23 Aug 31 16:55 /etc/alternatives/mail -> /usr/bin/mail.mailutils and the ultimate target is in a package: $ apt-file search /usr/bin/mail.mailutils mailutils: /usr/bin/mail.mailutils -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222179 Title: /usr/bin/mail has no package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1222179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222181] Re: /usr/bin/mail ignores aliases in $HOME/.mailrc
Interesting question. Ubuntu definitely supported $HOME/.mailrc aliases in version 10.04 (with its installed postfix). Also, the "mail" command has supported $HOME/.mailrc since the 1980s, even pre-Linux. It would be (IMHO) pretty unwise/unlikely to drop support for a config file that Linux scripts worldwide have depended on for decades. That would be like bash dropping support for $HOME/.bashrc. Is /usr/bin/mail even part of postfix? It's not in any postfix package in 13.04 (see bug #1222179) but somehow gets installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222181 Title: /usr/bin/mail ignores aliases in $HOME/.mailrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1222181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222169] Re: at -l intermittently prints "Cannot stat in /var/spool/cron/atjobs: No such file or directory"
** Changed in: at (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222169 Title: at -l intermittently prints "Cannot stat in /var/spool/cron/atjobs: No such file or directory" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at/+bug/1222169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222181] [NEW] /usr/bin/mail ignores aliases in $HOME/.mailrc
Public bug reported: 1. Put an alias in $HOME/.mailrc alias foo m...@whatever.com 2. Try to mail the alias: $ echo hello | /usr/bin/mail -s testing foo 3. Read /var/log/mail.log and see "foo" bounce as an unknown user: Sep 7 11:15:39 mycomputer postfix/local[9707]: EE038F6028B: to=, relay=local, delay=0.1, delays=0.07/0/0/0.03, dsn=5.1.1, status=bounced (unknown user: "foo") 4. However, my other mail programs, such as Emacs VM, respect the aliases in $HOME/.mailrc. ** Affects: postfix (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222181 Title: /usr/bin/mail ignores aliases in $HOME/.mailrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1222181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222180] [NEW] postfix package produces errors in ubuntu-bug
Public bug reported: $ ubuntu-bug postfix ERROR: hook /usr/share/apport/package-hooks/postfix.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook symb['add_info'](report, ui) File "/usr/share/apport/package-hooks/postfix.py", line 50, in add_info for k,v in extra_info.iteritems(): AttributeError: 'dict' object has no attribute 'iteritems' ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: postfix 2.10.0-3 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sat Sep 7 11:27:09 2013 InstallationDate: Installed on 2013-08-31 (6 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: postfix UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: postfix (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/1222180 Title: postfix package produces errors in ubuntu-bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1222180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222179] Re: /usr/bin/mail has no package
This old debian bug may be related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339012 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222179 Title: /usr/bin/mail has no package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1222179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222179] [NEW] /usr/bin/mail has no package
Public bug reported: The /usr/bin/mail has no package. "apt-file-search /usr/bin/mail" produces no package that owns /usr/bin/mail. Also "ubuntu-bug /usr/bin/mail" reports: ubuntu-bug: error: /usr/bin/mail does not belong to a package. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: postfix 2.10.0-3 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sat Sep 7 11:23:25 2013 InstallationDate: Installed on 2013-08-31 (6 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: postfix UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring ** Bug watch added: Debian Bug tracker #339012 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339012 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222179 Title: /usr/bin/mail has no package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1222179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222169] [NEW] at -l intermittently prints "Cannot stat in /var/spool/cron/atjobs: No such file or directory"
Public bug reported: Intermittently, when I run: $ at -l it prints this error message for some of its jobs: Cannot stat in /var/spool/cron/atjobs: No such file or directory Example output: $ at -l 13Fri Nov 1 21:00:00 2013 a jsmith 5 Wed Sep 11 21:00:00 2013 a jsmith 32Tue Sep 10 07:00:00 2013 a jsmith 11Mon Oct 21 21:00:00 2013 a jsmith 15Sat Feb 1 21:00:00 2014 a jsmith 14Fri Nov 15 09:00:00 2013 a jsmith Cannot stat in /var/spool/cron/atjobs: No such file or directory To reproduce, run "at -l" 10-20 times in rapid succession. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: at 3.1.13-2ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sat Sep 7 10:51:07 2013 InstallationDate: Installed on 2013-08-31 (6 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: at UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission denied: '/etc/at.deny'] ** Affects: at (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/1222169 Title: at -l intermittently prints "Cannot stat in /var/spool/cron/atjobs: No such file or directory" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at/+bug/1222169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222169] Re: at -l intermittently prints "Cannot stat in /var/spool/cron/atjobs: No such file or directory"
When the error message appears, some of the at jobs are missing from the displayed list. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222169 Title: at -l intermittently prints "Cannot stat in /var/spool/cron/atjobs: No such file or directory" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at/+bug/1222169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222169] Re: at -l intermittently prints "Cannot stat in /var/spool/cron/atjobs: No such file or directory"
Sorry, this was due to (my) user error. You can close this bug report. I recently built this machine and naively transferred some at jobs from another machine. They had the wrong file permissions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1222169 Title: at -l intermittently prints "Cannot stat in /var/spool/cron/atjobs: No such file or directory" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at/+bug/1222169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969359] Re: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock)
I can confirm this error message occurs in Ubuntu 13.04 64-bit while running VMware Workstation 10, each time that the mouse pointer crosses onto, or off of, the VMware window. (gnome-settings-daemon:5101): libappindicator-CRITICAL **: app_indicator_set_label: assertion `IS_APP_INDICATOR (self)' failed However, my CPU does not spike to 100%, at least as far as I can tell. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969359 Title: [keyboard]: gnome-settings-daemon consumes 100% cpu (and blinking numlock) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/969359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1222137] [NEW] gnome-screensaver emits repeated error, gtk_widget_set_visible: assertion `GTK_IS_WIDGET (widget)' failed
Public bug reported: I found this 20+ times in .xsession-errors after leaving the screensaver running overnight. (gnome-screensaver:5633): Gtk-CRITICAL **: gtk_widget_set_visible: assertion `GTK_IS_WIDGET (widget)' failed ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-screensaver 3.6.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sat Sep 7 08:24:38 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 600 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-08-31 (6 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (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/1222137 Title: gnome-screensaver emits repeated error, gtk_widget_set_visible: assertion `GTK_IS_WIDGET (widget)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1222137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175386] Re: .xsession fills up with gstreamer junk, then system effectively dies
This bug just crashed my system, growing ~/.xsession to 450GB until my disk filled to 100%. Will removing rhythmbox prevent it from happening? $ sudo apt-get remove rhythmbox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175386 Title: .xsession fills up with gstreamer junk, then system effectively dies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1175386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221503] [NEW] completion with ubuntu-bug complains about missing release-upgrade.py
Public bug reported: To reproduce the problem, type this command at a shell prompt (DO NOT PRESS ENTER AFTERWARD): $ ubuntu-bug and with the cursor at the end of the line, press the TAB key. The following errors appear: egrep: /usr/share/apport/symptoms/dist-upgrade.py@: No such file or directory egrep: /usr/share/apport/symptoms/release-upgrade.py@: No such file or directory If you clear the completion rules with "complete -r", this problem goes away. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: bash-completion 1:2.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Thu Sep 5 22:04:37 2013 InstallationDate: Installed on 2013-08-31 (5 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash-completion (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/1221503 Title: completion with ubuntu-bug complains about missing release-upgrade.py To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1221503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1221502] [NEW] bash completion escapes the dollar sign preceding a variable when it shouldn't
Public bug reported: Run these commands to reproduce the problem: $ touch xxx $ ls $PWD/x(now press TAB) The line completes like this: ls \$PWD/xxx with a slash in front of the dollar sign. If you run "complete -r", the problem goes away, and the line completes as: ls $PWD/xxx ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: bash-completion 1:2.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Thu Sep 5 22:00:18 2013 InstallationDate: Installed on 2013-08-31 (5 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash-completion (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/1221502 Title: bash completion escapes the dollar sign preceding a variable when it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1221502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1219529] [NEW] df -x tmpfs fails to exclude udev (/dev)
Public bug reported: The command: $ /bin/df -x tmpfs should exclude all filesystems of type tmpfs. The udev filesystem mounted at /dev is of this type: $ stat -f /dev File: "/dev" ID: 0Namelen: 255 Type: tmpfs Block size: 4096 Fundamental block size: 4096 Blocks: Total: 4109101Free: 4109098Available: 4109098 Inodes: Total: 4109101Free: 4108501 However, df still displays this filesystem: $ df -l -x tmpfs Filesystem 1K-blocks Used Available Use% Mounted on ... udev 1643640412 16436392 1% /dev ... ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: coreutils 8.20-3ubuntu5 ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sun Sep 1 15:05:40 2013 InstallationDate: Installed on 2013-08-31 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: coreutils (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/1219529 Title: df -x tmpfs fails to exclude udev (/dev) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1219529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 867806] Re: df -h permission denied error
The "adduser" workaround (#23) doesn't work under Ubuntu 13.04 because /run/user/lightdm is mode 700. :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/867806 Title: df -h permission denied error To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/867806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 500069] Re: USB file transfer causes system freezes; ops take hours instead of minutes
Referencing my previous post (#107): never mind. Something else is wrong with my machine. ALL disk writes are 1MB/second, even on my internal SSD RAID. So it's not just external drives. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/500069 Title: USB file transfer causes system freezes; ops take hours instead of minutes To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/500069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 500069] Re: USB file transfer causes system freezes; ops take hours instead of minutes
gonssal (#104): On 13.04 (live CD), I ran "sudo modprobe ehci_hcd" and copied files from an internal SSD to an external USB3 drive. I get super-slow 1 MB/second transfer rates. I boot the same computer into Windows 7 (it's dual boot) and I get 150MB/sec. I get the same problem if I use eSATA or Firewire (the external drive has all three connections): slow on 13.04, fast on Windows 7. If I boot on a Knoppix 7.2 CD, however... FAST FAST FAST transfer speed. Knoppix is 3.9 kernel, while 13.04 is 3.8. I also tried the Ubuntu nightly build of 13.10 today (kernel 3.11), and it had the same slowness problem as 13.04. I also tried #106 (echo "never" > "/sys/kernel/mm/transparent_hugepage/enabled") and it made no difference. My vendor blames the ASmedia Chipset on my motherboard, which he says Linux has "rudimentary at best" support for. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/500069 Title: USB file transfer causes system freezes; ops take hours instead of minutes To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/500069/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs