[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
The workaround for me was to disable vt_handoff in /etc/grub.d/10_linux* (i.e. set vt_handoff=0 in both places near the top of the file). That resolved the issue completely. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1133065] Re: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled
This is still happening in Ubuntu 19.10, and I'm all but certain it will continue to happen with 20.04 when I upgrade to it. I'll verify next weekend when I finally have time for the upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133065 Title: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1133065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810649] Re: Regression in Cosmic onwards: build ffmpeg 4 with external headers for NVENC
Will this be backported to Eoan? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810649 Title: Regression in Cosmic onwards: build ffmpeg 4 with external headers for NVENC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1810649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829409] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1829409/+attachment/5264322/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829409 Title: xfsdump doesn't allow levels beyond 0-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829409] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1829409/+attachment/5264317/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829409 Title: xfsdump doesn't allow levels beyond 0-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829409] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1829409/+attachment/5264316/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829409 Title: xfsdump doesn't allow levels beyond 0-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829409] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1829409/+attachment/5264318/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829409 Title: xfsdump doesn't allow levels beyond 0-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829409] Re: xfsdump doesn't allow levels beyond 0-9
apport information ** Tags added: apport-collected disco ** Description changed: Hi! I've found, quite surprised, that xfsdump doesn't allow dump level numbers outside of the range [0-9]. Given that even storing that number requires a full byte (8 bits), it boggles the mind why more numbers aren't supported. The usefulness of supporting more numbers (24? even 255...) is for taking hourly delta snapshots of live filesystems using xfsdump as a backup measure. With a simple script one can write a backup that takes a full dump (level 0) of the filesystem for the first backup of a given date, and all other backups during that day are incrementals (levels are > 0 ... i.e. the hour of the day the backup is taken). However, given that the tool only supports [0-9] as the backup level, this seems like an arbitrary limitation. Is there a real, technical limitation that this level is adhering to? Cheers! + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: gdm3277 F pulseaudio + diego 3916 F pulseaudio + /dev/snd/pcmC0D0p: diego 3916 F...m pulseaudio + /dev/snd/controlC1: gdm3277 F pulseaudio + DistroRelease: Ubuntu 19.04 + InstallationDate: Installed on 2019-04-20 (26 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + MachineType: ASUS All Series + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=1e9e8db1-15c8-4369-b27b-1a797cfe8561 ro quiet splash ipv6.disable=1 crashkernel=512M-:192M vt.handoff=1 + ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.0.0-13-generic N/A + linux-backports-modules-5.0.0-13-generic N/A + linux-firmware1.178.1 + RfKill: + 3: hci0: Bluetooth + Soft blocked: no + Hard blocked: no + Tags: disco + Uname: Linux 5.0.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 09/15/2017 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 3801 + dmi.board.asset.tag: Default string + dmi.board.name: RAMPAGE V EXTREME + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd09/15/2017:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnRAMPAGEVEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: ASUS MB + dmi.product.name: All Series + dmi.product.sku: All + dmi.product.version: System Version + dmi.sys.vendor: ASUS ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1829409/+attachment/5264313/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829409 Title: xfsdump doesn't allow levels beyond 0-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829409] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1829409/+attachment/5264319/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829409 Title: xfsdump doesn't allow levels beyond 0-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829409] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1829409/+attachment/5264323/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829409 Title: xfsdump doesn't allow levels beyond 0-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829409] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1829409/+attachment/5264320/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829409 Title: xfsdump doesn't allow levels beyond 0-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829409] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1829409/+attachment/5264321/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829409 Title: xfsdump doesn't allow levels beyond 0-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829409] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1829409/+attachment/5264324/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829409 Title: xfsdump doesn't allow levels beyond 0-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829409] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1829409/+attachment/5264325/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829409 Title: xfsdump doesn't allow levels beyond 0-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829409] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1829409/+attachment/5264314/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829409 Title: xfsdump doesn't allow levels beyond 0-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829409] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1829409/+attachment/5264315/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829409 Title: xfsdump doesn't allow levels beyond 0-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829409] [NEW] xfsdump doesn't allow levels beyond 0-9
Public bug reported: Hi! I've found, quite surprised, that xfsdump doesn't allow dump level numbers outside of the range [0-9]. Given that even storing that number requires a full byte (8 bits), it boggles the mind why more numbers aren't supported. The usefulness of supporting more numbers (24? even 255...) is for taking hourly delta snapshots of live filesystems using xfsdump as a backup measure. With a simple script one can write a backup that takes a full dump (level 0) of the filesystem for the first backup of a given date, and all other backups during that day are incrementals (levels are > 0 ... i.e. the hour of the day the backup is taken). However, given that the tool only supports [0-9] as the backup level, this seems like an arbitrary limitation. Is there a real, technical limitation that this level is adhering to? Cheers! ** Affects: linux (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/1829409 Title: xfsdump doesn't allow levels beyond 0-9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810649] Re: ffmpeg 4 requires external headers for NVENC
All the more reason this issue should be easily fixable by referencing that package as a builddep... again, unless licensing issues come into play. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810649 Title: ffmpeg 4 requires external headers for NVENC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1810649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810649] Re: ffmpeg 4 requires external headers for NVENC
The help at https://askubuntu.com/questions/778100/how-to-install- compile-nvenc-in-ubuntu is how I got to build working packages in my system (19.04 fresh install). Hopefully this gets fixed shortly. Maybe come up with a .deb that includes the NVENC headers so they're easier to incorporate into the base build? Dunno if any licensing issues would apply, though... Cheers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810649 Title: ffmpeg 4 requires external headers for NVENC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1810649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802321] Re: libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting...
Still present in 19.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802321 Title: libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdvd-pkg/+bug/1802321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828082] [NEW] FFMPEG no longer supports nvenc hwardware encoding out of the box
Public bug reported: FFMPEG previously supported NVENC encoding (nvenc, h264_nvenc, hevc_nvenc, nvenc_hevc) out-of-the-box, but no more. I had to follow this tutorial (https://askubuntu.com/questions/778100/how-to-install- compile-nvenc-in-ubuntu) to build them. Naturally this is becoming tedious as each time FFMPEG is updated, new packages need to be (re-)built to enable the codecs again. This is important since some dependent software programs rely specifically on those codecs. Thanks. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ffmpeg 7:4.1.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Tue May 7 10:17:56 2019 InstallationDate: Installed on 2019-04-18 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: ffmpeg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ffmpeg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828082 Title: FFMPEG no longer supports nvenc hwardware encoding out of the box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1828082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
If unloading-and-reloading the r8169 module solves the problem for you, here's a workaround that does it automatically for you upon resume from suspend: 1) Create a file /etc/systemd/system/fix-r8169.service with the following contents: BEGIN FILE [Unit] Description=Fix RTL-8169 Driver on resume from suspend After=suspend.target [Service] User=root Type=oneshot ExecStartPre=/sbin/modprobe -r r8169 ExecStart=/sbin/modprobe r8169 TimeoutSec=0 StandardOutput=syslog [Install] WantedBy=suspend.target # END FILE # 2) Execute the following command: sudo systemctl enable fix-r8169.service Cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752772 Title: r8169 ethernet card don't work after returning from suspension To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691505] [NEW] os-prober doesn't see Windows installations in an EFI system
Public bug reported: On a multiboot installation of Ubuntu Yakkety and Windows using UEFI, everything was working properly. Upon update to Zesty, os-prober was unable to locate the Windows partition and thus Grub (2.02~beta3-4ubuntu2 and previous Zesty versions) wasn't generating the correct bootable entries for it. I edited /usr/lib/os-probes/mounted/efi/20microsoft to fix the issue by updating it to the latest GRUB's expectations. The original script only output 3 columns: the device name, the label, and "Windows". GRUB was expecting 4 columns: the device name + EFI path (separated with @), the label, "Windows", and "efi". The script needed to be modified to properly handle these changes. I'm attaching the updated script, which works with both giving the device name and the EFI mount path, producing what I believe to be the correct output for both. This updated prober script fixes the issue by correctly chaining to the Windows boot manager. OS-prober also has an issue where the scripts in the "efi" directory (/usr/lib/os-probes/mounted/efi) aren't called, but instead need to be "moved" (copied) into the parent directory. This is a gap that needs bridging (i.e. make os-prober also run those scripts automatically). The expectation is that running "update-grub" would result in all available boot options being detected and accounted for as per what grub supports. Clearly that wasn't happening until the aforementioned script was fixed and placed in the right location. Cheers! ** Affects: os-prober (Ubuntu) Importance: Undecided Status: New ** Tags: dual-boot grub os-prober windows ** Attachment added: "20microsoft" https://bugs.launchpad.net/bugs/1691505/+attachment/4878388/+files/20microsoft -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691505 Title: os-prober doesn't see Windows installations in an EFI system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1691505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 834852] Re: gnome-shell crashed with SIGABRT in raise()
Forgot to mention, I'm using 3 monitors side-by-side (running at 120Hz), so that may also be a factor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/834852 Title: gnome-shell crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/834852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 834852] Re: gnome-shell crashed with SIGABRT in raise()
This bug is still happening in Ubuntu 14.04 with gnome-shell 3.10.4-0ubuntu5.2, using Citrix's icaclient v13.2.1.328635 whenever the client attempts to open a remote application window. I'm using an nVidia GTX 780 TI with the closed-source drivers (version 352.30), in x64 mode. How can I provide further debugging info (gnome-shell logs, ICA client logs, etc?) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/834852 Title: gnome-shell crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/834852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321713] Re: docky keeps crashing!
Confirmed on: Description:Ubuntu 14.04.1 LTS Release:14.04 docky-2.2.0-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321713 Title: docky keeps crashing! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docky/+bug/1321713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.
This bug needs to be fixed for those of us that don't use unity and only rely on gnome-shell. The problem seems to have been diagnosed to compiz, and thus the fix should be focused there so that it's not unnecessarily tied to unrelated packages (i.e. unity, as was the fix mentioned above). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/741869 Title: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/741869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155819] Re: Plugging in Logitech G930 USB headset breaks mouse click behaviour
The problem has been narrowed down to when the headset is actually charging - either through to the computer's USB ports or via a wall- socket charger (any micro-USB charger with 0.5A output will suffice). When the headset is unplugged (i.e. fully wireless), everything works fine. But when the headset is plugged in, the symptoms emerge. I will provide further information later today after I make some time to investigate more fully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1155819 Title: Plugging in Logitech G930 USB headset breaks mouse click behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1155819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1133835] Re: Ubuntu 12.10 immediately wakes up after suspend
This bug appears to be present in Saucy, using kernel 3.11.0-13 on x86_64 (x79 chipset). Suspend works well for the most part, but sometimes it goes stubborn and wakes immediately after suspend is requested (I can confirm that there are no scripts returning non-zero from pm's sleep.d and such). When it does work, it works like a charm (mostly, USB sometimes doesn't come back properly, but that's another story). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133835 Title: Ubuntu 12.10 immediately wakes up after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1133835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175122] Re: Doesn't work with Google 2-Factor Authentication
Still seeing this with gnome-online-accounts-3.8.3-2 on Saucy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175122 Title: Doesn't work with Google 2-Factor Authentication To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1175122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174648] Re: network settings, vpn modules don't load.
Nevermind my last comment. It appears that someone else had replaced the original packages with the ones from the gnome3-team/gnome3 ppa, and those did need the mentioned workaround. The VPN indicator also seems to have been fixed by rolling back the packages and the workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174648 Title: network settings, vpn modules don't load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1174648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174648] Re: network settings, vpn modules don't load.
I can confirm that on Ubuntu Saucy with gnome-control- center-3.8.5-0ubuntu1~saucy the problem persists. A workaround was to hard-link the files to the correct location (/usr/lib/x86_64-linux- gnu/NetworkManager/) from the installation location from the plugin packages (/usr/lib/NetworkManager/). Of note: I'm not using Unity - I'm using gnome-shell. Another secondary issue is that the VPN indicator for an OpenConnect VPN on the NetworkManager drop-down doesn't accurately reflect the status of the VPN. The full dialog from Network Settings does reflect it accurately, and allow control over the link. As a result, the NM icon on the notification bar remains as a lock (i.e. indicating the VPN is on) regardless of the actual status. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174648 Title: network settings, vpn modules don't load. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1174648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1133065] Re: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled
No effect for the default volume levels setting, the same behavior continues (tested repeatedly). No idea how to test the other thing you mention, since there's no mention of PCM Capture anywhere in those pulseaudio files. Can you offer up a concrete example of what you'd like me to add, and to which file? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133065 Title: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1133065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1133065] Re: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled
The simplest definition of the bug is that after bootup, the actual state of the emu20k2 hardware is not accurately reflected in the software (alsamixer, alsactl store). The easiest observable effect (in my case) is the PCM Capture switch - it shows off even though it's functioning as if it were on. Other differences between hardware and software may be exist, but I've not detected them (nor have I searched). Toggling the switch on, then off, fixes the issue and syncs between hardware and software. However, using alsactl restore has no effect even if the configuration being restored contains the instructions to set the switch to off, and even if the force parameter is used (which is the default anyway). I wonder if alsactl compares the hardware state to the new state intended and avoids setting the switch value as an optimization... I'm testing your latest now, will report its effects. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133065 Title: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1133065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1133065] Re: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled
Ok...your latest suggestion (pulseaudio analog-input.conf.common modifications) had no effect. The defect is still present. Let me know if you'd like me to test something else. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133065 Title: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1133065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1133065] Re: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled
You lost me - what's the o'clock capture switch? How do I set it? What are the permissible values? It's not documented in the alsactl man page either. If you give me an example I'll be more than happy to test and relay the results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133065 Title: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1133065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1133065] [NEW] Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled
Public bug reported: Upon boot, the EMU20K2's PCM input channel is enabled (unmuted), but it shows as disabled (muted) in alsamixer. One has to enable it and disable it in alsamixer in order to ensure sound does not leak out. This is unaffected by alsactl store/restore - even if the asound.state file includes information explicitly turning the PCM input off, alsactl restore fails to automatically fix the issue. One must manually go in and turn PCM input on, then off, to ensure it's really off. This has been the case for a few Ubuntu releases now. I'm reporting it precisely because it seems it's not been reported (or at least, not getting attention). ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-sound ** Attachment added: Alsa stored state. Even using this state will not cause the EMU20K2 chip to turn off its PCM input automatically. https://bugs.launchpad.net/bugs/1133065/+attachment/3547006/+files/asound.state ** Project changed: launchpad = alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133065 Title: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1133065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1133065] Re: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled
There would be a simple workaround if any of the command-line utilities for alsa would allow me to change specific mixer settings. A script could easily be devised to simply turn PCM Input on, then off, and that would be that. Sadly, to my knowledge no such utility exists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133065 Title: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1133065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1133065] Re: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133065 Title: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1133065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1133065] Re: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133065 Title: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1133065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1133065] Re: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled
Yes, precisely. Take this sequence: Start up the machine Boot to Ubuntu Log in Open sound input settings (gnome-control-center sound, input tab) Play some music The input indicator moves with the music clearly denoting that the PCM capture is enabled. However, alsactl store produces an asound.state file in which the PCM switch is turned off. Opening up alsamixer also shows the item as off. Same with amixer cget. Using alsactl to restore a correct asound.state does NOT fix the problem, but if I turn the switch on, then off again (via alsamixer, or amixer, regardless), correct functioning is restored - PCM capture is disabled. However, if I reboot, the problem shows up again. I haven't tested logout-login after fixing the problem (i.e. if it causes the issue or not), but I don't think it does (will test that shortly). The workaround is now to have a script that runs at login, turning the switch on, then off, using amixer (new discovery on my part). However this is only applicable to my case in which I want PCM input to be turned off at the beginning. Other users might want it turned on and/or other input means (microphone, line-in) turned off instead. The issue here is that state isn't being properly restored to where it should - either something is altering the card's state post-alsa initialization and state restore, without alsa's knowledge, or alsa isn't restoring the state properly. Hope this info helps. I'll run the logout-login test shortly and relay the results. Cheers! Thanks for the quick reply! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133065 Title: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1133065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1133065] Re: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled
As expected, login-logout had no effect. Therefore, it's safe to assume the bug only manifests on a fresh boot. This reinforces the idea that it's either something changing the card's state behind ALSA'S back, or ALSA not properly restoring state to the card. The fact that alsactl restore fails to fix the problem but amixer cset works, seems to suggest that alsactl restore may be where the problem lies. Cheers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133065 Title: Default mixer settings for EMU20K2 enable PCM Input on boot while showing it as disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1133065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994864] Re: Choppy video with Totem in 12.04 Precise Pangolin
Yes, it still occurs with nVidia drivers at 295.49, even 295.53. Videos are also choppy in standalone totem. gst123 works fine, so it would appear that the problem is within totem itself and not the gstreamer libraries. mplayer-based players work fine (except mplayer2). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994864 Title: Choppy video with Totem in 12.04 Precise Pangolin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/994864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 949134] Re: Window resizing leads to freeze on RDP sessions in precise
This also seems to happen when using VNC as well, so it seems to either be common to VNC and RDP, or protocol-agnostic. The solution is, however, to kill the remmina process - this seems to clear things up. I've run into this type of bug before with Eclipse, where on a right- click the UI would freeze completely. That's how I learned that killing the culprit is the solution. The problem is that the culprit is sometimes not obvious - especially when you have multiple processes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/949134 Title: Window resizing leads to freeze on RDP sessions in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/949134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994864] [NEW] Choppy video with Totem in 12.04 Precise Pangolin
Public bug reported: When trying to play MP4 videos captured from my Galaxy Nexus and copied to the local hard drive, video playback in Totem is choppy. VLC has no problem. Videos used to work fine in Totem in Natty and Oneiric. It appears that Totem is maxing out the core upon which it's running (cpu usage just over 25%... between 26% and 28% on a quad-core system). My video setup is dual nVidia GeForce 580 GTX's in SLI (SLI is not active), with dual monitors, using nvidia's driver (NOT nouveau...separate story - it fails miserably and locks up every time). I'm not sure how to gather additional information to help debug the issue, but if you ask, I can definitely try to provide as much information as possible. I've attached a short example video that should suffice to illustrate the issue. ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: choppy totem video -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994864 Title: Choppy video with Totem in 12.04 Precise Pangolin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/994864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994864] Re: Choppy video with Totem in 12.04 Precise Pangolin
** Attachment added: VID_20120429_171350.mp4 https://bugs.launchpad.net/bugs/994864/+attachment/3130829/+files/VID_20120429_171350.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994864 Title: Choppy video with Totem in 12.04 Precise Pangolin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/994864/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990708] [NEW] Failed to upgrade from 11.10 to 12.04 after upgrading from 11.04 to 11.10
Public bug reported: I skipped Oneiric Ocelot when I learned that Unity was fairly hard to turn off. Today I tried to do the upgrade path to Precise, only to get stopped by this error. There were no errors reported during the upgrade to Oneiric. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: update-manager 1:0.152.25.9 ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22 Uname: Linux 3.0.0-17-generic x86_64 NonfreeKernelModules: nvidia rr64x ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sat Apr 28 13:41:32 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: Upgraded to oneiric on 2012-04-28 (0 days ago) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990708 Title: Failed to upgrade from 11.10 to 12.04 after upgrading from 11.04 to 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/990708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990708] Re: Failed to upgrade from 11.10 to 12.04 after upgrading from 11.04 to 11.10
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990708 Title: Failed to upgrade from 11.10 to 12.04 after upgrading from 11.04 to 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/990708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 900550] Re: mtp-probe missing from libmtp build for Natty (1.0.6-2)
No, no messages in the log. The only reason I realized mtp-probe was missing was b/c I was trying to test my own udev rules (from the aforementioned workarounds), and while doing so I saw the message that certain rules were failing to apply because mtp-probe was missing. The issue is simple and I've fixed it in my own version of the package: add the mtp-probe file to the manifest for the libmtp8 package (or, failing that, mtp-tools), so that it gets bundled with the package. That's the whole problem - the file is built, and the built file works. It's just not rolled into the package at assembly time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/900550 Title: mtp-probe missing from libmtp build for Natty (1.0.6-2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/900550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 900550] Re: mtp-probe missing from libmtp build for Natty (1.0.6-2)
Sorry, I misunderstood your question. The answer to your question is no. Those messages you're seeing are indicative of some other USB- related problem since mtp-probe appears to be invoked properly, but is hanging for some reason and forcing udevd to kill it after a timeout expires. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/900550 Title: mtp-probe missing from libmtp build for Natty (1.0.6-2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/900550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 900550] [NEW] mtp-probe missing from libmtp build for Natty (1.0.6-2)
Public bug reported: As confirmed by the build logs at https://launchpadlibrarian.net/66810099/buildlog_ubuntu-natty- amd64.libmtp_1.0.6-2_BUILDING.txt.gz and https://launchpadlibrarian.net/66809838/buildlog_ubuntu- natty-i386.libmtp_1.0.6-2_BUILDING.txt.gz (I'm sure the others as well), mtp-probe is built, and even installed (evidently with the aim of including it in the package). However, it's not included in any of the produced .deb artifacts. This results in MTP-based devices not being easily from Natty (Galaxy tab, Xoom, Galaxy Nexus, etc), since the udev rules installed with the libmtp8 package directly and expressly reference /lib/udev/mtp-probe (this would suggest that the right place for it is the libmtp8 package, not mtp-tools). Furthermore, users are required to implement convoluted workarounds involving fuse, mtpfs, and manual creation of udev rules. This can be cumbersome and risky as well for non-power users. The fix is simple: include the built executable in the package (it's already being built anyway...just not packaged!). ** Affects: libmtp (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/900550 Title: mtp-probe missing from libmtp build for Natty (1.0.6-2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/900550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 349767] Re: external USB hard drive disconnects
Hi, all! Any news on whether this will be backported to 2.6.38 for Natty? At this point I'm reluctant to upgrade to Oneiric (b/c I don't like to be forced into using Unity, which I've not quite warmed up to yet), but I'd still like to enjoy this fix. Please advise. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/349767 Title: external USB hard drive disconnects To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/349767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858247] Re: Mounting SMB:// shares from a Mac, via GVFS, doesn't allow copying of data in either direction
Btw...this defect seems to be a Gnome (GVFS) defect more than a Samba defect - although smbclient has similar problems. The only thing that works for sure is mount.cifs with the above flags. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/858247 Title: Mounting SMB:// shares from a Mac, via GVFS, doesn't allow copying of data in either direction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/858247/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 858247] Re: Mounting SMB:// shares from a Mac, via GVFS, doesn't allow copying of data in either direction
Btw...this defect seems to be a Gnome (GVFS) defect more than a Samba defect - although smbclient has similar problems. The only thing that works for sure is mount.cifs with the above flags. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/858247 Title: Mounting SMB:// shares from a Mac, via GVFS, doesn't allow copying of data in either direction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/858247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858247] [NEW] Mounting SMB:// shares from a Mac, via GVFS, doesn't allow copying of data in either direction
Public bug reported: Mac OS X 10.7 (Lion) changed Samba for Apple's proprietary SMB stack. This stack has incompatibilities with the default smb:// mount modes supported by Samba and Gnome VFS. If I mount the system via Nautilus, opening the location smb://computer/share, I can see the file list and navigate it, but I can neither copy to nor from the machine (error is NT_STATUS_NOT_SUPPORTED, reflected in an error dialog with the message Function not implemented. If I mount the filesystem using mount.cifs, adding the options noserverino,nounix,sec=ntlmssp, then I can access all of the information fine on the far end. It is possible that this bug could go away if using Samba 3.6 - which fully supports SMB2 - but I've not been able to verify it because there are no Samba 3.6 packages for Natty or Oneric yet, and because I've been reluctant to roll my own Samba packages. Is there a way to configure GVFS to use a set of mounting options when connecting to a specific resource? I.e. when connecting to this server, use these options (like the ones mentioned above)? ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/858247 Title: Mounting SMB:// shares from a Mac, via GVFS, doesn't allow copying of data in either direction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/858247/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 858247] Re: Mounting SMB:// shares from a Mac, via GVFS, doesn't allow copying of data in either direction
I've just tried Samba 3.6.0 from Debian experimental, and the problem persists. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/858247 Title: Mounting SMB:// shares from a Mac, via GVFS, doesn't allow copying of data in either direction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/858247/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 858247] [NEW] Mounting SMB:// shares from a Mac, via GVFS, doesn't allow copying of data in either direction
Public bug reported: Mac OS X 10.7 (Lion) changed Samba for Apple's proprietary SMB stack. This stack has incompatibilities with the default smb:// mount modes supported by Samba and Gnome VFS. If I mount the system via Nautilus, opening the location smb://computer/share, I can see the file list and navigate it, but I can neither copy to nor from the machine (error is NT_STATUS_NOT_SUPPORTED, reflected in an error dialog with the message Function not implemented. If I mount the filesystem using mount.cifs, adding the options noserverino,nounix,sec=ntlmssp, then I can access all of the information fine on the far end. It is possible that this bug could go away if using Samba 3.6 - which fully supports SMB2 - but I've not been able to verify it because there are no Samba 3.6 packages for Natty or Oneric yet, and because I've been reluctant to roll my own Samba packages. Is there a way to configure GVFS to use a set of mounting options when connecting to a specific resource? I.e. when connecting to this server, use these options (like the ones mentioned above)? ** Affects: samba (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/858247 Title: Mounting SMB:// shares from a Mac, via GVFS, doesn't allow copying of data in either direction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/858247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 858247] Re: Mounting SMB:// shares from a Mac, via GVFS, doesn't allow copying of data in either direction
I've just tried Samba 3.6.0 from Debian experimental, and the problem persists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/858247 Title: Mounting SMB:// shares from a Mac, via GVFS, doesn't allow copying of data in either direction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/858247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 854344] Re: Gwibber 3.0.0.1 incorrectly storing timestamps in SQLite database
I get it - the problem is the message source (Twitter, in this particular case), not Gwibber. Fair enough. So is there an API from the actual service(s) to attempt to get the timezone configured for the account? What I'm thinking is that Gwibber *should* (ideally) store all timestamps relative to UTC if possible. This would make things consistent throughout. Then again, that depends on being able to get the message timestamps in UTC format from the source in the first place or, at least, have the information available to discern that value from the received information. Does this make sense? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/854344 Title: Gwibber 3.0.0.1 incorrectly storing timestamps in SQLite database To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/854344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 854344] Re: Gwibber 3.0.0.1 incorrectly storing timestamps in SQLite database
To-whit, I found this: https://dev.twitter.com/docs/api/1/get/account/settings The JSON object contains timezone information which can be used to determine which timezone the account is configured to. Thus, it can be used to calculate the UTC time that the message came in under. That's Twitter down... Perhaps you guys know this quicker/better than I: do the other services supported by Gwibber also return the timestamp wrong? If so, then which of them don't provide the ability to determine which timezone the timestamp comes in? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/854344 Title: Gwibber 3.0.0.1 incorrectly storing timestamps in SQLite database To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/854344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 854344] Re: Gwibber 3.0.0.1 incorrectly storing timestamps in SQLite database
Ditto for Facebook: http://developers.facebook.com/docs/reference/api/user/ I'm almost positive all the others contain this information 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/854344 Title: Gwibber 3.0.0.1 incorrectly storing timestamps in SQLite database To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/854344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 854344] [NEW] Gwibber 3.0.0.1 incorrectly storing timestamps in SQLite database
Public bug reported: While researching to build a script that would automatically purge messages older than X amount of time from the SQLite database, I found that the from the epoch timestamps being stored in messages.time aren't really from the epoch. As per all definitions, the epoch starts at 1/1/1970 00:00:00.000 GMT (the key point being GMT). Gwibber is storing the correct timestamp, but not taking the active timezone into account. That is to say, it's storing the epoch number into the database as if the local time were in GMT regardless of the truth. Assume a configured system timezone of CST. The current query returns the correct values for the message dates: select time, datetime(time, 'unixepoch') from messages order by time asc; However, clearly this is incorrect as the system is NOT in the GMT timezone. The timestamps stored should be relative GMT. This next query should be the correct one, in order to account for the timezone difference. However, the results are (predictibly) off by 6 hours (in the case of CST, which is the timezone delta): select time, datetime(time, 'unixepoch', 'localtime') from messages order by time asc; The 'localtime' argument instructs SQLite to take that timezone delta into account. (as per instructions from http://www.sqlite.org/lang_datefunc.html) The problem is that now, in order to create my purge script, I have to take into account the timezone that I'm running in, as opposed to simply saying delete the messages older than X hours. While this might appear to be a minor inconvenience, this defect makes it impossible to share the script as a black box solution for other users, since now the script would have to be configured for each user individually, to account for each of their own timezones. Not to mention to account for timezone shifts. ** Affects: gwibber Importance: Undecided Status: New ** Affects: gwibber (Ubuntu) Importance: Undecided Status: New ** Also affects: gwibber (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/854344 Title: Gwibber 3.0.0.1 incorrectly storing timestamps in SQLite database To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/854344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 813553] Re: Xorg freeze with Awesome WM
This bug also affects compiz - Awesome WM isn't the only one. This seems to be triggered by multiple flash elements in open browsers, and is a recent development (i.e. didn't happen when natty was first installed). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/813553 Title: Xorg freeze with Awesome WM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/813553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 804880] Re: 3D graphics cause EQ overflowing on Sandybridge Desktop
This bug also happens when using nvidia hardware (GTX 580). 100% CPU usage on Chromium when viewing flash videos after a while (i.e. youtube, etc). Firefox is also affected which leads me to think that it could be the flash plugin, not chromium or the video driver(s). Also using a Logitech mouse - I've seen other threads where this is seen as a contributing factor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/804880 Title: 3D graphics cause EQ overflowing on Sandybridge Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/804880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 508939] Re: Wrong colors when printing
I can confirm this as well with an HP OfficeJet 6500 Plus, using the HPLIP driver package, on 11.04 (Natty). Printing the same file from eVince produces the correct color output. Telling Acrobat to Let printer choose colors half-fixes the problem, but there are still incorrect colors being printed - i.e. the colors printed are closer to what's expected, but still incorrect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/508939 Title: Wrong colors when printing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/508939/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778446] Re: [SB-XFi - Creative X-Fi, playback] Sound is distorted -- (Echo with garble)
I'm having the same problem with Natty, and the issue happens randomly. However, it is possible that while the issue is happening (i.e. playing a video), other applications are able to output sound correctly while the distorted audio is being played back (discovered this today). I'll update with more information as I find it. Also, feel free to request information of me and I'll try to help provide it as best I can. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/778446 Title: [SB-XFi - Creative X-Fi, playback] Sound is distorted -- (Echo with garble) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
