[Bug 1966066] Re: audio from external sound card is distorted
I have this issue too. Hardware is a different external USB DAC (not Focusrite): $ lsusb | grep DAC Bus 005 Device 004: ID 08bb:2704 Texas Instruments PCM2704 16-bit stereo audio DAC Symptoms: Clicking sounds. Irregular but pretty frequent, up to once a second. It happens on kernel 5.13.0-37, but it goes away if I revert to 5.13.0-35. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966066 Title: audio from external sound card is distorted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Please open the new bug and provide a link so I can follow the progress and test the solution -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Status file too ** Attachment added: "status.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+attachment/5435346/+files/status.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Done! I see Nov 18 14:24:37 pop-offs ubuntu-appindicat...@ubuntu.com[32755]: discord1, Impossible to lookup icon for 'discord1_33-panel' in path /tmp/.org.chromium.Chromium.PSxy7s Nov 18 14:24:37 pop-offs ubuntu-appindicat...@ubuntu.com[32755]: unable to update icon for discord1 Nov 18 14:24:51 pop-offs ubuntu-appindicat...@ubuntu.com[32755]: discord1, Impossible to lookup icon for 'discord1_39-panel' in path /tmp/.org.chromium.Chromium.cZ6PNp Nov 18 14:24:51 pop-offs ubuntu-appindicat...@ubuntu.com[32755]: unable to update icon for discord1 Please see attached. ** Attachment added: "newmessages.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+attachment/5435342/+files/newmessages.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
Why does the issue still occur with the fix? The severity is lessened but it is still there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
sudo apt install gnome-shell-extension-appindicator/focal seemed to restore it properly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
After installing the deb (oddly asking me to downgrade to your supplied version) and logging back in, I was greeted with an error from my HP printer drivers saying there is no detected system tray and it's unable to start (attached). Discord and MegaSync still appear in the tray so I don't know what that's all about. The stutter/lag caused by discord still exists but it's MUCH improved. It's much harder to perceive, but it's certainly still there. I'd estimate the lags are 5-10x shorter in duration. I am testing on an AMD 5950X CPU so it's not caused by a lack of processing power. How do I restore the package back to my system maintainers version? ** Attachment added: "Screenshot from 2020-11-17 21-18-54.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+attachment/5435124/+files/Screenshot%20from%202020-11-17%2021-18-54.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849142] Re: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon"
I'm running Pop OS 20.04 with this bug, I'd be happy to test this if I knew how to install the patch. Do I just need to enable proposed packages? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849142 Title: appindicator extension slows down GUI spamming the log with "[AppIndicatorSupport-FATAL] unable to lookup icon ..." or "Impossible to lookup icon" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1849142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901346] [NEW] package indicator-sound 12.10.2+18.10.20180612-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal
Public bug reported: error opening applicatio manager ProblemType: Package DistroRelease: Ubuntu 20.04 Package: indicator-sound 12.10.2+18.10.20180612-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 24 21:10:41 2020 Dependencies: DpkgTerminalLog: dpkg: error processing package indicator-sound (--remove): package is in a very bad inconsistent state; you should reinstall it before attempting a removal dpkg: too many errors, stopping ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting a removal InstallationDate: Installed on 2020-10-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: indicator-sound Title: package indicator-sound 12.10.2+18.10.20180612-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901346 Title: package indicator-sound 12.10.2+18.10.20180612-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1901346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872870] Re: Ubuntu 20.04 latest update mouse pointer leaves square trails on desktop
Hi Ted, I was experiencing this too! Your fix worked for me... disabled zoom: no more trails. I seemed to only get the on the desktop background ... each set of trails would clear themselves after a second or two, and they seem to be flickering a bit, so perhaps they are only appearing in the display buffers. Maybe to do with NVidia proprietary drivers? Cheers, Fred -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872870 Title: Ubuntu 20.04 latest update mouse pointer leaves square trails on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1872870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866457] Re: gnome-shell crashes every time I unlock my screen
Enabling animations seems to work around the bug. I can lock and unlock my screen manually without crashing gnome-shell. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866457 Title: gnome-shell crashes every time I unlock my screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866457] Re: gnome-shell crashes every time I unlock my screen
Yes, I do have animations disabled. I'll re-enable them and see if that works around the crashes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866457 Title: gnome-shell crashes every time I unlock my screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866457] [NEW] gnome-shell crashes every time I unlock my screen
Public bug reported: After a recent "apt upgrade", for about 4 days gnome-shell crashes every time I lock/unlock my screen. Disabling the screen lock lets me run X and Wayland sessions with GNOME indefinitely. Manually locking my screen or letting it lock automatically causes gnome-shell to crash when I try to unlock it. When it crashes, it hangs for a long time without updating the mouse cursor (probably writing the large core dump), then finally dies and the window system restarts and I can log in. I've disabled all GNOME extensions and tried some other configuration changes but I can't find a work-around except to avoid the lock screen. Description:Ubuntu Focal Fossa (development branch) Release:20.04 gnome-shell: Installed: 3.35.91-1ubuntu2 Candidate: 3.35.91-1ubuntu2 Version table: *** 3.35.91-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 Date: Sat Mar 7 07:30:22 2020 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2018-02-28 (737 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-12-13 (84 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866457 Title: gnome-shell crashes every time I unlock my screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866457] Re: gnome-shell crashes when I lock my screen
apport doesn't ever successfully upload the full crash dump. It always gets an HTTP 503 at the end, which I figure is the server timing out from the 1 GB core dump upload. I can provide a backtrace, thread dump, or other info from the dump if it would be helpful. ** Summary changed: - gnome-shell crashes when I lock my screen + gnome-shell crashes every time I unlock my screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866457 Title: gnome-shell crashes every time I unlock my screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837087] Re: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1
For what it's worth I'm getting a very similar issue on Linux Mint Cinnamon after the update from 19.1 to 19.2. The error is: cinnamon: ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. I've found that the positions of monitors in a dual monitor setup dictates whether or not the DE crashes on startup. See this thread: https://github.com/linuxmint/cinnamon/issues/8754 Hopefully the problem is identical for you guys and a patch can fix both issues at once. ** Bug watch added: github.com/linuxmint/cinnamon/issues #8754 https://github.com/linuxmint/cinnamon/issues/8754 ** Also affects: cinnamon (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/1837087 Title: gnome-shell crashed with assertion failure ../src/gallium/drivers/radeonsi/si_state_viewport.c:239: si_emit_guardband: Assertion `left <= -1 && top <= -1 && right >= 1 && bottom >= 1' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1837087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832426] Re: "Program" is not responding when debugging in gdb
Hi Marco, No, the warning/dialog shows repeatedly. I think if I'm debugging a program, ubuntu and gnome-shell should never tell me the window is not responding. I might focus the window to use it, or to set it above all others so I can watch it. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832426 Title: "Program" is not responding when debugging in gdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832426] [NEW] "Program" is not responding when debugging in gdb
Public bug reported: I believe this is a regression for #1740869 is not responding window is constantly showing when debugging a program I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint this window shows up and I can't get it to stop asking me to close the program. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 19.04 Release:19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-shell: Installed: 3.32.1-1ubuntu1~19.04.1 Candidate: 3.32.1-1ubuntu1~19.04.1 Version table: *** 3.32.1-1ubuntu1~19.04.1 500 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 3) What you expected to happen When I hit a breakpoint in gdb, the program should stop. 4) What happened instead The program stops and ubuntu asks me if i want to kill the program. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 11 22:03:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-08 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832426 Title: "Program" is not responding when debugging in gdb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831026] [NEW] package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: steam crashed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-browsed 1.8.3-2ubuntu3.5 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue May 28 23:22:14 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-07-28 (305 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: cups-filters Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831026 Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1831026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822743] Re: partman: needs to ignore entire /cdrom device
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822743/+attachment/5251983/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822743 Title: partman: needs to ignore entire /cdrom device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822743] Re: partman: needs to ignore entire /cdrom device
** Attachment added: "partman" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822743/+attachment/5251984/+files/partman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822743 Title: partman: needs to ignore entire /cdrom device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822743] Re: partman: needs to ignore entire /cdrom device
** Attachment added: "ubiquity debug log" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822743/+attachment/5251985/+files/debug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822743 Title: partman: needs to ignore entire /cdrom device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822743] [NEW] partman: needs to ignore entire /cdrom device
Public bug reported: In the file /lib/partman/init.d/30parted the $path (which is a partition, NOT a device) is checked to see if it matches the beginning of $line (which contains the list of devices from the command "parted_devices"). Then, if a match is found, it is later checked if this is mounted to "/cdrom", and if so it is later "dropped" IF it is determined that the free space on the drive is less than 16777216. There are a few problems with this approach, which I attempt to rectify in the attached patch: 1. Since parted_devices lists "/cdrom" to a device (/dev/sdb) not to a partition (/dev/sdb1) but $path is always a partition (/dev/sdb1, /dev/sdb2, etc.) then no match is ever made, and thus /cdrom is never checked to be excluded. 2. I suggest that at any time the device containing "/cdrom" should be excluded, not only if it has more freespace than 16777216. The reason is that newer releases of usb-creator-gtk and other tools such as mkusb will leave the remainder of the disk as "free", meaning that if you write the installer to a 32GB thumbdrive, it will then have enough freespace that makes partman think it is a good candidate for installation. But I don't think it likely that a user will ever want to install to the device containing the livecd (/cdrom) and if they do, then they can go to the "something else" advanced partitioning to specify so. The real bug may be that on ubiquity's partition selection screen (NOT the advanced "something else") that it sees the MAIN hard drive (/dev/sda), and prompts to install side by side but then when clicking that option the installer USB (/dev/sdb) is selected as the target, it is partitioned, and confusion ensues. Regardless, the above points are fixed with the attached patch so I hope you will consider including it. This was written against Ubuntu 18.04 ubiquity 18.04.14.12. I will add /var/log/syslog and /var/log/partman of the problem (using our remastered installer) to hopefully make it more clear. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Patch added: "patch for 30parted" https://bugs.launchpad.net/bugs/1822743/+attachment/5251953/+files/30parted-remove-cdrom-device.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822743 Title: partman: needs to ignore entire /cdrom device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822743] Re: partman: needs to ignore entire /cdrom device
** Attachment added: "Modified 30parted to be used with patch" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822743/+attachment/5251954/+files/30parted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822743 Title: partman: needs to ignore entire /cdrom device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819363] Re: uefi: os-prober doesn't skip cdrom iso9660 type
** Changed in: os-prober (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/1819363 Title: uefi: os-prober doesn't skip cdrom iso9660 type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1819363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819363] Re: uefi: os-prober doesn't skip cdrom iso9660 type
I only stick to "LTS" so it is for version 1.74ubuntu1 for bionic. Sorry I neglected to see if any updates had been made in any possible newer version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819363 Title: uefi: os-prober doesn't skip cdrom iso9660 type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1819363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819363] Re: uefi: os-prober doesn't skip cdrom iso9660 type
** Patch added: "patch for 50mounted-tests" https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1819363/+attachment/5245397/+files/50mounted-tests-iso9660.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819363 Title: uefi: os-prober doesn't skip cdrom iso9660 type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1819363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819363] Re: uefi: os-prober doesn't skip cdrom iso9660 type
Attached is a patch for this issue. I am noting that this patch is necessary when running in uefi mode to install shim-signed / grub-efi- amd64-signed / etc. ** Attachment added: "modified 50mounted-tests" https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1819363/+attachment/5245396/+files/50mounted-tests -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819363 Title: uefi: os-prober doesn't skip cdrom iso9660 type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1819363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819363] [NEW] uefi: os-prober doesn't skip cdrom iso9660 type
Public bug reported: File: /usr/lib/os-probes/50mounted-tests Issue: on a respin of Ubuntu (yes, not supported but I believe the issue could possibly affect Ubuntu as well) when booting the USB in 'secure boot' UEFI mode, when installing, the update-grub command gives the following error which then stops the installer with the all-too-common "failed to install grub-efi-amd64-signed" to /target error: grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map. The problem is, however, that in this case /dev/sdb1 is the live system's "cdrom" and should NOT be probed! So I propose the following addition to 50mounted-tests that would ensure "optical media" partitions would be skipped by os-prober: elif [ "$types" = iso9660 ]; then debug "$1 is an optical media iso9660 partition; skipping" exit 0 With this addition, update-grub no longer returns an error which I am hoping will make ubiquity not give the following error: ubiquity: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 127 ubiquity: Errors were encountered while processing: ubiquity: grub-efi-amd64-signed ubiquity: E: Sub-process /usr/bin/dpkg returned an error code (1) I hope this addition will help others that have issues with secure boot mode! I have not created a patch yet but can if it seems acceptable. ** Affects: os-prober (Ubuntu) Importance: Undecided Status: New ** Tags: grub secure ubiquity uefi ** Tags added: grub ubiquity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819363 Title: uefi: os-prober doesn't skip cdrom iso9660 type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1819363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816386] Re: [SRU] Unable to install virtualbox-guest-x11-hwe on 18.04.2 LTS with HWE
+Gianfranco, Thanks for rebuilding to fix the dependency issue. I am unclear if this will be pushed to the main repos or do we need to get the updated packages from your ppa? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816386 Title: [SRU] Unable to install virtualbox-guest-x11-hwe on 18.04.2 LTS with HWE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-hwe/+bug/1816386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778274] [NEW] snd_hda_codec_realtek hdaudioC0D0: Unable to sync register
Public bug reported: Hi. I'm running Ubuntu MATE 16.04 running kernel `4.4.0-128-generic`. Since applying updates this morning I'm now unable to shut my machine down cleanly. If I shut down or restart, the error `snd_hda_codec_realtek hdaudioC0D0: unable to sync register` is output 3 times and the machine doesn't power down. I have to finish the shutdown manually by holding the power button. Wasn't sure which debug steps to follow for this error, but this is the corresponding extract from `/var/log/kern.log`: ``` Jun 22 21:14:04 leonard kernel: [ 37.378508] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -5 Jun 22 21:14:04 leonard kernel: [ 37.378876] snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1 Jun 22 21:14:04 leonard kernel: [ 37.379239] snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1 Jun 22 21:14:04 leonard kernel: [ 37.379602] snd_hda_codec_hdmi hdaudioC0D2: HDMI: invalid ELD buf size -1 Jun 22 21:14:04 leonard kernel: [ 37.405753] snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 Jun 22 21:14:04 leonard kernel: [ 37.405873] snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 Jun 22 21:14:04 leonard NetworkManager[904]: [1529698444.9269] ModemManager disappeared from bus ``` I made the report using `ubuntu-bug linux` so hopefully this will provide the necessary debug info. If I need to post more info, let me know what you need. Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 1660 F pulseaudio CurrentDesktop: MATE Date: Fri Jun 22 21:19:43 2018 HibernationDevice: RESUME=UUID=6bc8046c-253e-4b27-bb37-27d8e02c255d InstallationDate: Installed on 2017-01-25 (513 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:1112 Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N24_25BU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic.efi.signed root=UUID=f03f5e5c-4a97-462b-8e17-63e66a434dc9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.19 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Tag 12345 dmi.board.name: N24_25BU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd12/01/2016:svnNotebook:pnN24_25BU:pvrNotApplicable:rvnNotebook:rnN24_25BU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.name: N24_25BU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1778274 Title: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629509] Re: Cannot mount overlay with upperdir on overlay
I switched to devicemapper as the storage driver. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629509 Title: Cannot mount overlay with upperdir on overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515331] Re: localechooser-apply: Don't default to am (Amharic) for Ethiopia (ET)
** Tags added: ubiquity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515331 Title: localechooser-apply: Don't default to am (Amharic) for Ethiopia (ET) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1515331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515331] Re: localechooser-apply: Don't default to am (Amharic) for Ethiopia (ET)
Is there any ability to get this looked at before 18.04? I have to instruct everyone here to choose a location in the US during installation so that the language settings are setup correctly. Then after install, we go to Date and Time to set the timezone to Ethiopia. Since Ubuntu is wanting diagnostics from users on install country, Ethiopia will never be counted! We have over 100 installs now and will likely double this or even more in the next year. It would be GREAT if we could correctly be identified as being in Ethiopia but due to this bug it won't be reported correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515331 Title: localechooser-apply: Don't default to am (Amharic) for Ethiopia (ET) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1515331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430068] Re: Unable to launch gnome-system-monitor
Not sure what causes the problem or how to fix it manually but a reboot cleared it up for me (same exact error message from terminal as original reporter). So after reboot it is working fine again. This is Ubuntu 16.04, btw. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430068 Title: Unable to launch gnome-system-monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1430068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
The fix from the fourdollars ppa is also working for me: Lenovo x230. I ran the stress test before applying the fix and confirmed that wifi was non-functioning after the 30 suspend / wake cycles and needed the "sudo wpa_cli scan" to activate it again. I then added the ppa and applied the update to network-manager and then rebooted. Then I ran the stress test again and after the 30 suspend / wake cycles wifi was still functioning correctly! This is using 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/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
@fourdollars does this commit get applied to 16.04 proposed and then to backports? I (and I am sure others) would be happy to test this for xenial but I am unclear as to the path the patches follow to get to the main repositories. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1635781] Re: Arch Linux Dual-Boot fails to boot Arch
There is a possible solution here: http://askubuntu.com/a/842802/57704 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1635781 Title: Arch Linux Dual-Boot fails to boot Arch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1635781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656725] [NEW] attempted to download vlc and got the brokencount >0 message
Public bug reported: I dont know what happened. clicked on show updates (no entry symbol) and after about 5 minutes I received the prompt to record and send the bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.20 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Sun Jan 15 19:50:50 2017 InstallationDate: Installed on 2017-01-13 (2 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656725 Title: attempted to download vlc and got the brokencount >0 message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1656725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327801] Re: Bightness and contrast settings have no effect
As reported at Bug #1340161 the problem is solved for a Canon LiDE 110 scanner using Ubuntu 16.04 and simple-scan 3.20.0=0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327801 Title: Bightness and contrast settings have no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1327801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1340161] Re: brightness, contrast for Canon LIDE 110 not working
*** This bug is a duplicate of bug 1327801 *** https://bugs.launchpad.net/bugs/1327801 Brightness and Contrast adjustments for Canon LiDE 110 in Ubuntu 16.04, simple-scan 3.20.0-0ubuntu1 work perfectly! So I think this specific bug is solved, even though others with different scanner models are reporting problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1340161 Title: brightness, contrast for Canon LIDE 110 not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1340161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629509] Re: Cannot mount overlay with upperdir on overlay
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Xenial) 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/1629509 Title: Cannot mount overlay with upperdir on overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629509] Re: Cannot mount overlay with upperdir on overlay
Hmm, looking at the kernel source this seems intentional. See commit 76bc8e2843b66f8205026365966b49ec6da39ae7. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629509 Title: Cannot mount overlay with upperdir on overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629509] Re: Cannot mount overlay with upperdir on overlay
Yes, exists in 4.4.23-040423-generic as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629509 Title: Cannot mount overlay with upperdir on overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629509] [NEW] Cannot mount overlay with upperdir on overlay
Public bug reported: I have a docker setup using overlay as its storage driver. I mount an overlay in the container. Both the lower, upper and work directories are themselves on an overlay filesystem. This mount started to fail after upgrading to kernel 4.4.0-38 from 4.4.0-34 with the error message "overlayfs: filesystem on '/mnt/overlay/upper' not supported as upperdir". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaw 2257 F pulseaudio /dev/snd/controlC1: shaw 2257 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 30 20:06:03 2016 HibernationDevice: RESUME=UUID=f23b927f-5173-43fe-9269-8c7714fb0927 InstallationDate: Installed on 2016-07-23 (69 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. XPS13 9333 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=306f5ab9-de0e-4920-be20-3f4081e13c7e ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. ** Affects: linux (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/1629509 Title: Cannot mount overlay with upperdir on overlay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606309] Re: Difficult to access menu options for non-full screen apps on global menu bar
Yes, 'click to focus' is disabled. While verifying that setting in CompizConfig Manager I found the 'Focus Desktop' toggle and disabled it. This disabled the desktop from grabbing focus when traversing it with the mouse and fixed the problem. Thanks @azzar1 for pointing me in the right direction. ** Changed in: unity (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/1606309 Title: Difficult to access menu options for non-full screen apps on global menu bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1606309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1606309] [NEW] Difficult to access menu options for non-full screen apps on global menu bar
Public bug reported: In 16.04 it has become very hard to select menu options for apps that do not take up the full-screen using a mouse. Note that this is a problem only when you select to show menu options in the menu bar. The change of behavior causing the issue is that when the mouse moves from the app over the desktop, the menu bar changes to the options of the 'Ubuntu desktop'. In 14.04, even while the mouse traverses the desktop, the menu options displayed are those of the last application traversed with mouse (except, of course, the desktop), so accessing the menu options is easy. To access menu options with the mouse in 16.04 you must either full-screen the application or move the application so that its window touches the menu bar and then slide your mouse directly from the application to the menu bar. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: bar bot-comment desktop menu options ** Summary changed: - Impossible to access menu options for non-full screen apps on global menu bar + Difficult to access menu options for non-full screen apps on global menu bar ** Description changed: - 16.04 it has become very hard to select menu options for apps that do + In 16.04 it has become very hard to select menu options for apps that do not take up the full-screen using a mouse. Note that this is a problem only when you select to show menu options in the menu bar. The change of behavior causing the issue is that when the mouse moves from the app over the desktop, the menu bar changes to the options of the 'Ubuntu desktop'. In 14.04, even while the mouse traverses the desktop, the menu options displayed are those of the last application traversed with mouse (except, of course, the desktop), so accessing the menu options is easy. To access menu options with the mouse in 16.04 you must either full-screen the application or move the application so that its window touches the menu bar and then slide your mouse directly from the application to the menu bar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1606309 Title: Difficult to access menu options for non-full screen apps on global menu bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1606309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475993] Re: Freeze logout in Ubuntu 15.04
This issue remains in Ubuntu 16.04 (Unity). Using Cinnamon desktop there is no hang on logout. But using Unity there is up to a 90 second delay to get back to the login screen when logging out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475993 Title: Freeze logout in Ubuntu 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/diodon/+bug/1475993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573476] [NEW] Error installing GRUB ubuntu 16.04
Public bug reported: GRUB doesn't installs after installing ubuntu 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Fri Apr 22 14:18:13 2016 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_IN PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573476 Title: Error installing GRUB ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1573476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850065] Re: Brightness control on Toshiba Satellite L755
I had the same problem with a Satellite L755 (Intel only, no NVIDIA) and solved it by creating this file: /usr/share/X11/xorg.conf.d/20-intel.conf Giving it the following: Section "Device" Identifier "card0" Driver "intel" Option "Backlight" "intel_backlight" BusID "PCI:0:2:0" EndSection After reboot the brightness function keys work! Other posts indicated needing to add acpi_backlight=vendor to grub but I don't seem to need to modify any grub settings. Just the above file solves the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850065 Title: Brightness control on Toshiba Satellite L755 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/850065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 850065] Re: Brightness control on Toshiba Satellite L755
FYI that above fix was for Ubuntu 14.04 / Linux Mint 17, with the 3.19 kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/850065 Title: Brightness control on Toshiba Satellite L755 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/850065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1495781] Re: Can't move to trash in data partition
*** This bug is a duplicate of bug 1449112 *** https://bugs.launchpad.net/bugs/1449112 CzBiX can you clarify your patch? It works but I am having trouble following the logic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1495781 Title: Can't move to trash in data partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1495781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515331] Re: localechooser-apply: Don't default to am (Amharic) for Ethiopia (ET)
To be clear, the override for ET) should just be removed, then I assume the language will not be overridden and the user will get their choice they entered from the dialogs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515331 Title: localechooser-apply: Don't default to am (Amharic) for Ethiopia (ET) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1515331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515331] [NEW] localechooser-apply: Don't default to am (Amharic) for Ethiopia (ET)
Public bug reported: /usr/share/ubiquity/localechooser-apply now has these lines: # Somewhat unclear: Oromo has the greatest number of # native speakers; English is the most widely spoken # language and taught in secondary schools; Amharic is # the official language and was taught in primary # schools. ET) deflang=am ;; I am an expat IT worker living in Ethiopia and I can confirm that Ethiopia has 2 national languages: Amharic (am) and English (en). English is the primary language of instruction in secondary school and the *only* language of instruction at the University level. It is the defacto international language. Also, since MS Windows has not supported Amharic well, all computer systems here are using English US as the interface. In summary, there should be no hard-coded override to change the language to Amharic, even if a user chose English as the language during the ubiquity dialogs. Right now, when I choose English as the interface, it is set as the locale, but the language is set to Amharic. Hopefully this can be corrected before 16.04. We have a Linux revolution going on down here and everyone is confused why Amharic takes over even though they chose English during install :-) Regards from Ethiopia, "land of 13 months of sunshine" (kudos if you get that joke) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amharic english ethiopia language locale -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515331 Title: localechooser-apply: Don't default to am (Amharic) for Ethiopia (ET) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1515331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1509782] Re: Does not save drafts
You may want to report this bug at geary's main bug tracker. Here is a link to the Geary homepage, where you will find the links to bugzilla: https://wiki.gnome.org/Apps/Geary I am pretty certain they are not looking to much at launchpad. That said I have the same problem! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509782 Title: Does not save drafts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geary/+bug/1509782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514147] [NEW] appmenu-qt5 + gnome-shell: if installed vlc icon won't appear
Public bug reported: Using Gnome-Shell 3.16 in Ubuntu 15.10, removing appmenu-qt5 is the only way to get the vlc tray icon to show. You can confirm the problem by attempting to start vlc in the tray while using gnome-shell: vlc --qt-start-minimized With appmenu-qt5 installed, the following error is generated, and the vlc tray icon will NOT show (not even in the "drawer" at the bottom or by using "top icons" extension): qt4 interface error: cannot start minimized without system tray bar After removing appmenu-qt5 then vlc will be able to start properly with the above command (or starting normally will add the icon to the bottom 'legacy icon drawer' or to the panel using the "top icons" extension). So, what is lost by removing appmenu-qt5? Is unity affected? I am hoping to not cause a problem for a system with both Unity and Gnome-Shell installed. ** Affects: appmenu-qt5 (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-shell vlc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1514147 Title: appmenu-qt5 + gnome-shell: if installed vlc icon won't appear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1514147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307619] Re: Qt Creator Menu bar is missing at Gnome3 or KDE Desktop
I created a separate report for the appmenu-qt5 bug that prevents vlc from showing in the gnome-shell drawer or panel: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1514147 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307619 Title: Qt Creator Menu bar is missing at Gnome3 or KDE Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/lyx/+bug/1307619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307619] Re: Qt Creator Menu bar is missing at Gnome3 or KDE Desktop
Using Gnome-Shell 3.16 in Ubuntu 15.10, I can confirm that removing appmenu-qt5 is the only way to get the vlc tray icon to show. You can confirm the problem by attempting to start vlc in the tray: vlc --qt-start-minimized With appmenu-qt5 installed, the following error is generated, and the vlc tray icon will NOT show (not even in the "drawer" at the bottom or by using "top icons" extension): qt4 interface error: cannot start minimized without system tray bar After removing appmenu-qt5 then vlc will be able to start properly with the above command (or starting normally will add the icon to the bottom 'legacy icon drawer' or to the panel using the "top icons" extension). So, what is lost by removing appmenu-qt5? Is unity affected? I am hoping to not cause a problem for a system with both Unity and Gnome- Shell installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307619 Title: Qt Creator Menu bar is missing at Gnome3 or KDE Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/lyx/+bug/1307619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1253002] Re: Xorg crash when using Chrome
** Also affects: xorg-server (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/1253002 Title: Xorg crash when using Chrome To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1253002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1491999] Re: [P750ZM-G, Realtek ALC892, Black SPDIF Out, Rear] No sound at all
Since I have the same sound driver I think my solution may be correct. I didn't have sound and it turned out that somehow alsa had mixed up my headphone and microphone jack. Try sudo apt-get install alsa-tools-gui Then open with hdajackretask It was simple for me to switch the microphone with the headphone and everything started working. By the way I noticed this by plugging in my headphones into my microphone jack and all the sudden it was recognized as a headphone, but sound still didn't work because it was a microphone jack. I'm guessing you would of noticed if this was the case, but it took me a long time to try this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1491999 Title: [P750ZM-G, Realtek ALC892, Black SPDIF Out, Rear] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1491999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 762449] Re: Dash is visually hard to grasp and browse
As an update to this original bug, we are now targeting Gnome-Shell with the "gno-menu" extension specifically because of the inability for "computer illiterate" users (3rd world users new to computers doing literacy work in their own languages) being able to browse applications in the dash. The dash is just so overwhelming and confusing, even after turning off all the external data sources, shopping suggestions, etc. An application menu that is browsable not just searchable is a core requirement in our location. Here is the link to gno-menu that we are using: https://extensions.gnome.org/extension/608/gnomenu/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/762449 Title: Dash is visually hard to grasp and browse To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/762449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1293629] Re: [Regression] [Trusty] Unity can't be started from kdm
I haven't found out how to set XDG_CURRENT_DESKTOP from mdm (Linux Mint's fork of older gdm), so then when attempting to login to Gnome- Shell I am greeted with a black screen. However, doing this is a workaround (but still leaves XDG_CURRENT_DESTKOP unset): in /usr/share/upstart/sessions/gnome-session.conf change: instance $XDG_CURRENT_DESKTOP to: instance GNOME -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1293629 Title: [Regression] [Trusty] Unity can't be started from kdm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1293629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1484844] Re: MDM support for casper
UPDATE: As I learn more I have found that casper 1.340.2 is working fine, but that there is no support for mdm, the login manager for Linux Mint. Here is a patch to add that will make it work: /usr/share/initramfs-tools/scripts/casper-bottom/15autologin: Add in a MDM section like below: if [ -f /root/etc/mdm/mdm.conf ]; then # Configure MDM autologin MDMConfFile=/root/etc/mdm/mdm.conf AutomaticLoginParameters=AutomaticLoginEnable=true\n\ AutomaticLogin=$USERNAME\n\ TimedLoginEnable=false # Prevent from updating if parameters already present (persistent usb key) if ! $(grep -qs '^AutomaticLogin' $MDMConfFile); then sed -i s/\[daemon\]/\[daemon\]\n$AutomaticLoginParameters/ \ $MDMConfFile fi fi With that above addition, casper is auto logging in with MDM as the display manager. ** Summary changed: - casper 1.340.2 + trusty: with remastersys goes to login screen instead of direct to Live Session + MDM support for casper -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1484844 Title: MDM support for casper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1484844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1484844] [NEW] casper 1.340.2: with remastersys goes to login screen instead of direct to Live Session
Public bug reported: I use remastersys (yes I know it isn't supported anymore, but it still works fine with 14.04 trusty) to make custom ISOs. Last week after doing a dist-upgrade and then running remastersys, the resulting ISOs, would go to a login screen when starting the Live Session instead of booting all the way to the Live Session desktop. I have done this process many times for Ubuntu 14.04, and never had this problem, even though a google search will show several others in the past have had this issue. You can get around the login screen by using the remastersys ID from /etc/remastersys.conf and a password of blank, but this didn't work all the time for me (I think it is fairly reliable with lightdm, but we use mdm from LinuxMint, which would not accept the blank password and would stay stuck at the login screen). After a lot of trial and error in trying to isolate what changed, I have found that casper 1.340.2 is the source of the problem. If I hold casper at 1.340 like this: apt-mark hold casper ubiquity-casper After applying this command to my test machine, and then doing a dist- upgrade, and then running remastersys, the resulting ISOs boot correctly to the Live Session desktop. If, however, casper updates to 1.340.2, the resulting ISOs will go to the login screen and get stuck. I have attempted to scan the changes to casper and am not able to understand what is causing the problem, but it definitely is something to do with casper 1.340.2. ** Affects: casper (Ubuntu) Importance: Undecided Status: New ** Tags: remastersys -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1484844 Title: casper 1.340.2: with remastersys goes to login screen instead of direct to Live Session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1484844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1484844] Re: casper 1.340.2 + trusty: with remastersys goes to login screen instead of direct to Live Session
** Summary changed: - casper 1.340.2: with remastersys goes to login screen instead of direct to Live Session + casper 1.340.2 + trusty: with remastersys goes to login screen instead of direct to Live Session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1484844 Title: casper 1.340.2 + trusty: with remastersys goes to login screen instead of direct to Live Session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1484844/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979119] Re: 12.04: Resume Failure: Press any key to continue from suspend
@penalvch I will have them do so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979119 Title: 12.04: Resume Failure: Press any key to continue from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/979119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979119] Re: 12.04: Resume Failure: Press any key to continue from suspend
I am helping an individual remotely that has 3 of these Toshiba Tecra A9 laptops, all with Ubuntu 12.04.5, and all having the resume from suspend failure described here. So I am re-opening the bug as we have access to someone that can help to give more information. ** Changed in: linux (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979119 Title: 12.04: Resume Failure: Press any key to continue from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/979119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401355] Re: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux-gnu/libnvidia-opencl.so.331.113', which is also in package n
I have tried all the drivers that I can find and non of them seem to work. Is there some comand in a terminal that I can use to fix this problem? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401355 Title: package nvidia-opencl-icd-331-updates (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/i386-linux-gnu /libnvidia-opencl.so.331.113', which is also in package nvidia-opencl- icd-331 331.113-0ubuntu0.0.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1401355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1297302] Re: Orange squares around checkboxes and radio buttons
How can more people not be annoyed by this? It seems this bug is not getting traction but it is a bit embarrassing that the main theme of Ubuntu has such 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/1297302 Title: Orange squares around checkboxes and radio buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1297302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1405059] [NEW] nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build
Public bug reported: Graphics driver problem ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11 Uname: Linux 3.13.0-41-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-44-generic Date: Sun Dec 21 21:24:48 2014 InstallationDate: Installed on 2014-10-20 (64 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1405059 Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1405059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979119] Re: 12.04: Resume Failure: Press any key to continue from suspend
@penalvch Sorry but I no longer have access to the Toshiba Tecra A8 and Toshiba Tecra M10 laptops that had these issues. As there are others on this list that had me too comments I won't close the bug now, but maybe you would want to. I will leave it to you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979119 Title: 12.04: Resume Failure: Press any key to continue from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/979119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373663] Re: Inadequate locale settings
Agreed that there should be an option in Ubiquity to choose your locale. I am a US citizen in Ethiopia currently, so when I install here, even though I choose English (US) as my keyboard, when I first login to the system, my locale is Ethiopia and the system language is Amharic! I don't read Fidel well, so can barely get around to change to English! Whenever a person is in a location that is not their home (an expat) they will likely prefer to NOT use the local locale (except for system time!) Furthermore, even Ethiopian people often prefer English, as it is the international langauge and there is no Amharic Microsoft Windows, so they are familiar with English Microsoft Windows. In summary, giving the user an easy way to set their locale (at least default system language) is essential in Ubiquity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373663 Title: Inadequate locale settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1373663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 962270] Re: /usr/sbin/lightdm-session: 34: [: Linux: unexpected operator
@lj-pinho, Unfortunately that solution will not work if you have Bash- specific shell syntax in your .bash_profile (and why wouldn't you?). I'm currently having this same issue because of using `[[ ]]` instead of `[ ]` and source instead of `.`. I _knew_ there was a good reason I'd previously changed all my `[[ ]]` to `[ ]` in my `.profile` file. However, there's also a good reason to not have a `.bash_profile` and only have a `.profile` but I'm forgetting what that is at the moment. Can anyone enlighten me? I do use these dotfiles across Linux, Mac, FreeBSD and (not recently) Solaris, UX, AIX, Cygwin, MinGW. Mainly my dotfiles need to be portable across Linux and Mac. Cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/962270 Title: /usr/sbin/lightdm-session: 34: [: Linux: unexpected operator To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/962270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357804] Re: Ubuntu 14.04 does not support 2560x1080 resolution.
I don't know that much about packages... I hope xrandr covers it... ** Package changed: ubuntu = xrandr (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357804 Title: Ubuntu 14.04 does not support 2560x1080 resolution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrandr/+bug/1357804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357804] [NEW] Ubuntu 14.04 does not support 2560x1080 resolution.
Public bug reported: I recently installed Ubuntu 14.04 on a mac mini and bought a 2560 x 1080 ultrawide LG monitor for it. Problem is that it doesn't display the proper resolution, the maximum being 1920 x 1080 under ubuntu settings. Any suggestions on what I should do? Please give clear instructions as I am not an Ubuntu expert. My graphics card: NVIDIA Corporation C79 [GeForce 9400] If there is currently no solution, would someone please pass this on to the Ubuntu developers so that they start working on implementing this resolution into the operating system? Thank you, Ian ** 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/1357804 Title: Ubuntu 14.04 does not support 2560x1080 resolution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1357804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308348] Re: network settings indicator missing from panel
If it's been fixed, how do i install the patch? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308348 Title: network settings indicator missing from panel To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1308348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241811] Re: USB disk not automatically mounted after upgrade to 13.10
I also have this problem and if it is the same bug I have narrowed it down to lightdm. I am using Mint 17 (based on Ubuntu 14.04). Mint's default login manager is mdm (fork of gdm). With it, usb devices are auto-mounted just fine when plugged in. When I install lightdm and choose it as the login manager, after reboot then devices *do not auto-mount anymore*. Just as the previous poster, the dmesg output shows that the device is correctly found and attached, but not mounted. When I click on the device in Nautilus or Nemo, it will then mount just fine, but it needs this manual interaction. If I then uninstall lightdm, choosing mdm again as the display manager, upon reboot the auto-mounting of usb devices works just fine again. So it must be something in lightdm for me. A udev rule not finishing somehow triggered by lightdm? An upstart trigger involving lightdm that hangs things up? Any advice on where to look from here appreciated. ** Also affects: lightdm 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/1241811 Title: USB disk not automatically mounted after upgrade to 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1241811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241811] Re: USB disk not automatically mounted after upgrade to 13.10
@romano-giannetti I see now that you indicate you are not using lightdm. Can you confirm your login manager? If so we may have a different problem, but everything else seems identical. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241811 Title: USB disk not automatically mounted after upgrade to 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1241811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1316613] Re: com.canonical.desktop.interface scrollbar-mode corrupts gtk3 apps in non-Unity desktops
In 14.04 I am using Ambiance theme with Cinnamon, and in Cinnamon Settings there was definite corruption (black backgrounds on the tabs) that was solved by disabling overlay-scrollbars. Maybe there is something that Cinnamon Settings can be doing differently, but wanted to note that even with Ambiance theme there is this problem with certain apps. So, not just a theme problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1316613 Title: com.canonical.desktop.interface scrollbar-mode corrupts gtk3 apps in non-Unity desktops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1316613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244775] Re: huawei E1962 dongle to be plugged twice
This is affecting me also with a Huawei E1690 modem. It will be found by Network Manager only on even plug-ins (so, not found on 1st, 3rd, 5th plugins, but found on 2nd, 4th, 6th plugins). This is with Ubuntu 14.04 up-to-date as of 13 Feb, 2014. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244775 Title: huawei E1962 dongle to be plugged twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1244775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244775] Re: huawei E1962 dongle to be plugged twice
Forgot to note that this E1690 Modem was working fine in Ubuntu 12.04 (same machine). This is a bit older modem and starts as 12d1:1446, and is switched by usb-modeswitch to: 12d1:1001 (not the 12d1:1436 that ivano mentions for newer Huawei modems). UPDATE: OK, now it seems to be showing every time (so no problem). Will need to test a bit more. Maybe I am going crazy! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244775 Title: huawei E1962 dongle to be plugged twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1244775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244775] Re: huawei E1962 dongle to be plugged twice
UPDATE: I stand corrected. This E1690 modem is not mode-switched the FIRST time connected to the machine. Watching lsusb, the device just stays at its original ID of 12d1:1446 and never switches to 12d1:1001. But if I unplug it and replug it, the 2nd, 3rd, 4th, times it is always correctly switched to 12d1:1001 and then Mobile Broadband is displayed in the Network Manager. It is only this first time it sits a 12d1:1446 and is not switched. Maybe this is the same situation as the original poster, ivano, was seeing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244775 Title: huawei E1962 dongle to be plugged twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1244775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1244775] Re: huawei E1962 dongle to be plugged twice
I enabled usb-modeswitch logging in /etc/usb_modeswitch.conf, and tried again. After rebooting, the first plugin of the device (where it is not switched generates no log by usb-modeswitch at /var/log/usb_modeswitch*). The second plugin does generate a log, /var/log/usb_modeswitch.log). So, it seems to me that usb-modeswitch is not being triggered at all the first time the device is plugged in (rather than usb-modeswitch being triggered and not succeeding in switching the device). Is this then a udev issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1244775 Title: huawei E1962 dongle to be plugged twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1244775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979748] Re: [expected] VGA monitor only gets signal on boot (no “hot plugging”, no EDID)
I have downloaded and installed trusty 64 daily build (2013-01-07) on a real partition on the Toshiba Tecra M10 machine used to originally report this problem (so no variable to it being a VM or running from a LiveCD). When connecting an external monitor via VGA (after machine already running), Displays in System Settings now shows proper monitor identification, with the option to set correct resolution. From Displays it appears as if the monitor is Active. However, no signal is detected by the external monitor, and it is black. If I then restart (so machine boots with the monitor already connected), then all works as expected. Resolution is correct, and both the laptop display and the external monitor are active. So, the external monitor seems to be identified corrrectly, but when hot plugged no signal is sent to the external monitor until a reboot. So, this main component of the original bug report remains unsolved. Please let me know what tests I can perform to provide any more information. ** Summary changed: - [expected] VGA monitor only gets signal on boot (no “hot plugging”, no EDID) + [expected] VGA monitor only gets signal on boot (no signal when “hot plugging”) ** Summary changed: - [expected] VGA monitor only gets signal on boot (no signal when “hot plugging”) + VGA monitor only gets signal on boot (no signal when “hot plugging”) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979748 Title: VGA monitor only gets signal on boot (no signal when “hot plugging”) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/979748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979748] Re: VGA monitor only gets signal on boot (no signal when “hot plugging”)
@penalvch I added the edgers PPA, performed a dist-upgrade, rebooted, and still have the same results: hot plugging the monitor after already booted without it has it show correctly in Displays but there is *no* signal sent to the monitor. Only upon reboot does it receive the signal correctly. Should the laptop boot with the monitor plugged in, then disconnect the monitor, then later re-connect the monitor, it will behave correctly. So, it is only when booting without the monitor connected that it will not receive the signal after later being connected. Again, I am happy to perform any debugging or provide any requested logs should you advise on what steps to take for you to get the information you need. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979748 Title: VGA monitor only gets signal on boot (no signal when “hot plugging”) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/979748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184262] Re: [logind] times out too early, stuck in PrepareForSleep, causing network and other services to not resume
In my previous comment I said that Martin's package didn't fix my issue, but two days after I said that, the suspend-repeat loop seems to have gone away. Sometimes my wifi turns on automatically on resume, sometimes it doesn't. Overall, it's a much better experience, but there's still some work to do. Thanks, Martin! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: [logind] times out too early, stuck in PrepareForSleep, causing network and other services to not resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1184262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume
I installed Martin's package, but it doesn't fix the issue on my Thinkpad T420. After resume, the network isn't usable and I have to run nmcli nm sleep false to enable it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1184262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume
@Daniel Lombraña González (teleyinex) #66 however, if I suspend the machine again and resume it, after few seconds it starts again to suspend without me doing anything, leaving the machine in an unusable state. I get the same behavior on my Thinkpad T420. Sleep works great, but when I wake it up the network is disabled. When I re-enable NetworkManager (nmcli nm sleep false), the machine starts putting itself to sleep repeatedly. Having to manually enable wifi is a small annoyance, but the repeating- sleep behavior is extremely annoying. It can take 5 minutes of waking it back up before I can use it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1184262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1023165] Re: Can't change IBus input method using menu in Unity
I have since clarified that problem 2 from comment #4 above is not valid, and was related to the specific application we were using. So, in summary, there does NOT seem to be any issue with setting ibus as the keyboard input method in Language Support. But, problem 1 from comment #4 above regarding needing to use the Debian versions of ibus instead of the patched Ubuntu versions remains valid and true for Precise, Oneiric, and I am assuming others. Whatever is in the ubuntu patched version BREAKS gui use of ibus! I have re-packaged ibus from debian in my ppa, so anyone wanting to confirm it solves their problems is welcome to try the packages from the ppa (if you add the ppa, on next dist-upgrade it should pull them in automatically): https://launchpad.net/~wasta-linux/+archive/wasta -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1023165 Title: Can't change IBus input method using menu in Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1023165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007423] Re: ibus won't turn 'on' when in certain programs
Sorry for the double post above in comments 12 and 13. Björn is correct this does NOT seem LibreOffice related. I have since clarified that problem 2 from comment #13 above is not valid, and was related to the specific application we were using. So, in summary, there does NOT seem to be any issue with setting ibus as the keyboard input method in Language Support. But, problem 1 from comment #13 above regarding needing to use the Debian versions of ibus instead of the patched Ubuntu versions remains valid and true for Precise, Oneiric, and I am assuming others. Whatever is in the ubuntu patched version BREAKS gui use of ibus! I have re-packaged ibus from debian in my ppa, so anyone wanting to confirm it solves their problems is welcome to try the packages from the ppa (if you add the ppa, on next dist-upgrade it should pull them in automatically): https://launchpad.net/~wasta-linux/+archive/wasta I have also applied this comment to the related ibus bug 1023165 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007423 Title: ibus won't turn 'on' when in certain programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1007423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1189063] Re: f-spot full crash upon startup
I believe I have this fixed upstream, but there are some side effects from it that I'm trying to fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1189063 Title: f-spot full crash upon startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/f-spot/+bug/1189063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152538] Re: segmentation fault when trying to checkout
** Attachment added: crash report #1 from apport https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1152538/+attachment/3773489/+files/_usr_bin_svn.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152538 Title: segmentation fault when trying to checkout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1152538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152538] Re: segmentation fault when trying to checkout
** Attachment added: crash report #2 from apport https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1152538/+attachment/3773491/+files/_usr_bin_svn.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/1152538 Title: segmentation fault when trying to checkout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1152538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152538] Re: segmentation fault when trying to checkout
** Attachment added: strace output from running svn https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1152538/+attachment/3773492/+files/strace_svn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152538 Title: segmentation fault when trying to checkout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1152538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1152538] Re: segmentation fault when trying to checkout
Issue is occurring on an old platform, even with 'simple' commands like svn --help, svn--version: cat /proc/cpuinfo gives CPU Family 15 model 2 Mobile Intel (R) Pentium(R) 4 (ie this problem is occuring on a 32 bit system). which is in an HP nx9010 laptop. Lubuntu 12.10 is a fresh (done yesterday) install from the 'Alternate' CD (Oct 2012), plus ~200MBytes of updates from 'update-manager', AND the additional packages needed to install / use OpenWRT (all from the default Ubuntu repositories apart from 'jikes' which was downloaded direct from Debian). # lsb_version -rd Description:Ubuntu 12.10 Release:12.10 # svnadmin --version svnadmin, version 1.7.5 (r1336830) compiled Jun 22 2013, 03:54:33 Copyright (C) 2012 The Apache Software Foundation. This software consists of contributions made by many people; see the NOTICE file for more information. Subversion is open source software, see http://subversion.apache.org/ The following repository back-end (FS) modules are available: * fs_base : Module for working with a Berkeley DB repository. * fs_fs : Module for working with a plain file (FSFS) repository. # apt-cache policy subversion subversion: Installed: 1.7.5-1ubuntu2.1 Candidate: 1.7.5-1ubuntu2.1 Version table: *** 1.7.5-1ubuntu2.1 0 500 http://gb.archive.ubuntu.com/ubuntu/ quantal-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu/ quantal-security/main i386 Packages 100 /var/lib/dpkg/status 1.7.5-1ubuntu2 0 500 httModel (p://gb.archive.ubuntu.com/ubuntu/ quantal/main i386 Packages I am NOT running kdewallet which was the issue for another bug report in LP re svn issues; the --help and --version switches to svn should mean that it is not even looking at authentication stuff.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1152538 Title: segmentation fault when trying to checkout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subversion/+bug/1152538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883962] Re: cannot add m4a files
Seeing same problem with gtkpod 2.1.0 installed on Ubuntu 11.10 and gtkpod 2.1.2 on Lubuntu 12.10; trying to load data to an old iPod Photo Just before the error dialogue re .m4a files not being recognized, there is a couple of errors reported related to trying to write to the users home directory (eg /home/user ) and 'user.ext'. gtkpod also does not seem to be consistent in terms of the how/when/if it recognizes the mounted / loaded iPod; dmesg contains complaints about sending ioctl 2285 to a partition. Fix described above by keplicz works for me on the Lubuntu system (not yet tried the 11.10 machine). NOTE: you need ensure that whatever programme is creating the .m4a files, the mp3/mp4 'tag fields' are populated with artist name, track etc (not sure what the minimum requirement is). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883962 Title: cannot add m4a files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtkpod/+bug/883962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1059017] Re: python3.3 throws apport exception on each traceback
Deleting /usr/lib/python3.3/sitecustomize.py worked around this for me. Is there a reason why this workaround can't be included in the package itself? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1059017 Title: python3.3 throws apport exception on each traceback To manage notifications about this bug go to: https://bugs.launchpad.net/blender/+bug/1059017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 945678] Re: libgstreamer0.10-0 - cheese does not open and has memory leak.
same experience using a 11.10 system, Lenovo laptop, in-built camera. Attached from top shows how cheese INITIALLY takes near 100% of the CPU (Celeron 900 @ 2.2GHz), then 'not much' whilst near all the free RAM (system has 1GByte) AND swap space is consumed by cheese. No other applications running; tested was initiated on a newly booted system. Skype + VLC + guvcview all 'seem to work fine'. System becomes un-responsive (due to it thrashing the disk) until a run- away process killer kills cheese recovers the memory + swap space. ** Attachment added: CPU memory utilization of cheese (reported by top). https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/945678/+attachment/3534870/+files/cheese.lst -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/945678 Title: libgstreamer0.10-0 - cheese does not open and has memory leak. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/945678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930671] Re: video blank and menus greyed out in cheese
** Attachment added: gst-debug.log.bz2 https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/930671/+attachment/3531495/+files/gst-debug.log.bz2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930671 Title: video blank and menus greyed out in cheese To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/930671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930671] Re: video blank and menus greyed out in cheese
detail that should have been with the attachment: I have same issue with Ubuntu 11.10 on a Lenovo laptop with built-in camera; same Gtk warning message as indicated by the OP, but NO GUI or splash screen visible as cheese is started, so no way to access any 'check config' commands. If I turn on the 'video call' option in Skype, camera works fine; but it is usually off as link BW is 'not good enough'; only apps running when cheese app is tried are F'Fox, T'bird, the terminal console. Running with the --gst-debug=5 log option as suggested by hychen above generates a *** 400 *** Mbyte file; after the start-up period, cheese is taking over 80% of the CPU (Celeron 2.2GHz), log file size seems static; 'nothing magic' happens. There must be a lot of duplicate info/messages in the log as it has compressed down to less than 1MByte..(attached) I see a forum post here: http://ubuntuforums.org/showthread.php?t=2068818 where the OP (squakie in the forum) states his issue (with 12.04) was solved on upgrade to 12.10. Is it possible to get a backport / work-around for earlier versions ? (limited capabilities of my platform preclude moving to 3-D desktops). Bugzilla etc in other environments I have worked with give links to the changeset that fixed whatever issue was reported originally.. FTR, other info from my system: dmesg |grep 'video' [0.206120] pci :00:02.0: Boot video device [ 12.862718] Linux video capture interface: v2.00 [ 12.895972] uvcvideo: Found UVC 1.00 device Lenovo EasyCamera (090c:3371) [ 13.005371] usbcore: registered new interface driver uvcvideo [ 7166.558394] PM: resume of drv:uvcvideo dev:2-3:1.0 complete after 673.003 msecs [ 7166.558400] PM: resume of drv:uvcvideo dev:2-3:1.1 complete after 672.982 msecs ~$ lsusb 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:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 090c:3371 Feiya Technology Corp. ~$ lsmod |grep 'video' uvcvideo 67271 0 videodev 85626 1 uvcvideo video 19069 1 i915 ~$ lsmod |grep 'i915' i915 513895 3 drm_kms_helper 32889 1 i915 drm 192194 4 i915,drm_kms_helper i2c_algo_bit 13199 1 i915 video 19069 1 i915 ~$ ls -alrt /dev/video* crw-rw+ 1 root video 81, 0 2013-02-16 08:51 /dev/video0 ~$ uname -a Linux a_user 3.0.0-29-generic #46-Ubuntu SMP Tue Dec 4 12:17:31 UTC 2012 i686 i686 i386 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930671 Title: video blank and menus greyed out in cheese To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/930671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063589] Re: update-manager crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Activation of org.debian.apt timed out
this is happening to me with Lubuntu 12.10. Update manager runs in the background alerts each week of updates. I usually select 'remind me later'. Then when I run Synaptic etc to add specific packages there is a crash. It is then impossible to run the software updater to perform the 'pending upgrades', or Synaptic to add / remove packages. I found a work-around from 'actionparsnip' that is a script to download from dropbox, purging apt-cache etc; will post a link. Problem with this is that it seem to download a huge amount of data due to all packages being refreshed / re-fetched. 2nd time the crash occurred, the 'crash log' (which apport has sent to 'Ubuntu' automatically) gave me this specific bug reference. Why is it occurring ? (I have another machine running Ubuntu 11.10 that has never exhibited this). How to: - recover without having to refresh all packages = big download.. - stop it happening on the Lubuntu machine (pending 'proper' fix). thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063589 Title: update-manager crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Activation of org.debian.apt timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1063589/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
