[Bug 1970392] Re: 22.04 USB devices do not work after sleep on Dell XPS 13 9370
Thanks Kai-Heng. I have updated this and will keep you posted: $ sudo dmidecode -s bios-version 1.19.0 $ sudo dmidecode -s bios-release-date 03/22/2022 Devices that have been updated successfully: • System Firmware (1.12.1 → 1.19.0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970392 Title: 22.04 USB devices do not work after sleep on Dell XPS 13 9370 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970392] Re: 22.04 USB devices do not work after sleep on Dell XPS 13 9370
Just by way of update, this does not happen very often. It happened to me again today after I have changed around which ports I have things in, perhaps for the first time since I reported this a month ago. The same Thunderbolt ports are not working after suspend, but the USB-C only port works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970392 Title: 22.04 USB devices do not work after sleep on Dell XPS 13 9370 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973340] [NEW] 22.04 obs-studio does not launch out of the box with Wayland
Public bug reported: Trying to launch OBS studio with the package installed from apt gives an error on Wayland. $ obs Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. Aborted (core dumped) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: obs-studio 27.2.3+dfsg1-1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 13 14:06:20 2022 InstallationDate: Installed on 2022-04-24 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: obs-studio UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: obs-studio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973340 Title: 22.04 obs-studio does not launch out of the box with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1973340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973340] Re: 22.04 obs-studio does not launch out of the box with Wayland
obs-studio installed via snap install obs-studio launches as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973340 Title: 22.04 obs-studio does not launch out of the box with Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1973340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972991] [NEW] 22.04 Totem crashes on launch (segmentation fault)
Public bug reported: Hello, Since upgrading (fresh reinstall) to 22.04, I have had issues with Totem crashing. I have not been able to pin down when it works and when it doesn't, as playing the same videos seems to work sometimes and not work others. After it crashes, trying to open it again normally does not work and trying to launch totem from the commandline gives a segmentation fault. Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Segmentation fault (core dumped) $ totem Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 11 13:10:48 2022 InstallationDate: Installed on 2022-04-24 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972991 Title: 22.04 Totem crashes on launch (segmentation fault) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1972991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972545] Re: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)
(And Firefox gave me a notification about hitting version 100, so it presumably did update) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972545 Title: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972545] Re: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)
** Attachment added: "As expected, closing and reopening Firefox makes it work as expected" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+attachment/5587903/+files/Screenshot%20from%202022-05-09%2013-44-45.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972545 Title: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972545] Re: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)
** Attachment added: "Screenshot of the dock" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+attachment/5587901/+files/Screenshot%20from%202022-05-09%2013-32-20.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972545 Title: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972545] [NEW] Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)
Public bug reported: I am using the Firefox Snap on a fresh install of 22.04 (using defaults, as far as I know). Normally, Firefox shows an indicator in the Dock showing that it is running (the orange dot) and gives the ability to choose between open windows. At the moment, I have Firefox windows open, but nothing is shown in the Dock (as if it is closed). My suspicion is that the snap was refreshed while running and this confused Gnome Shell. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 13:31:40 2022 InstallationDate: Installed on 2022-04-24 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "journalctl -b 0 > log" https://bugs.launchpad.net/bugs/1972545/+attachment/5587897/+files/log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972545 Title: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970392] Re: 22.04 USB devices do not work after sleep on Dell XPS 13 9370
Yes, I think that is correct. If you look at this diagram: https://www.dell.com/support/manuals/en-uk/xps-13-9370-laptop/xps-13-9370-setupandspecs/left?guid=guid-a06ee5db-8981-4955-86ab-82b36e5aff57=en-us I normally plug the monitor with keyboard into the port labelled 2 and the network adapter into the one labelled 3, both of which are apparently Thunderbolt ports (I do not have any Thunderbolt devices, so just use them as USB-C). The remaining port, which I said above works, is the port labelled 3 in this diagram: https://www.dell.com/support/manuals/en-uk/xps-13-9370-laptop/xps-13-9370-setupandspecs/right?guid=guid-b67143e0-0e2c-4025-899a-9819aca57baa=en-us and that is apparently USB-C instead of Thunderbolt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970392 Title: 22.04 USB devices do not work after sleep on Dell XPS 13 9370 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970942] [NEW] ubuntu-bug firefox gives error "No contact address has been provided"
Public bug reported: When I try to report a bug in Firefox on 22.04 with the Firefox Snap, it gives an error: "The problem cannot be reported: firefox is provided by a snap published by mozilla. No contact address has been provided; visit the forum at https://forum.snapcraft.io/ for help." I understand this is unexpected, as they do provide a contact address: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla and that this is the link that others are offered when running ubuntu-bug firefox ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashReports: 640:1001:124:9413623:2022-04-29 13:39:08.158073186 +0100:2022-04-29 13:39:09.174077949 +0100:/var/crash/_usr_bin_totem.1001.crash 600:117:124:37:2022-04-29 13:50:19.497838008 +0100:2022-04-29 13:38:42.086254937 +0100:/var/crash/_usr_bin_totem.1001.uploaded 664:1001:124:0:2022-04-29 13:39:09.158073230 +0100:2022-04-29 13:39:09.158073230 +0100:/var/crash/_usr_bin_totem.1001.upload CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 14:26:27 2022 InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screenshot from 2022-04-29 11-51-59.png" https://bugs.launchpad.net/bugs/1970942/+attachment/5585123/+files/Screenshot%20from%202022-04-29%2011-51-59.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970942 Title: ubuntu-bug firefox gives error "No contact address has been provided" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1970942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970392] [NEW] 22.04 USB devices do not work after sleep on Dell XPS 13 9370
Public bug reported: I have a Dell XPS 13 9370 that came with Ubuntu preinstalled. I have just completed a fresh install of 22.04 on it. When I suspend the laptop, the USB devices that were plugged in when I suspended do not work. Specifically, I had an Ethernet adapter and a USB-C monitor with a keyboard attached through it. The monitor display works as expected, but neither the keyboard nor the Ethernet adapter work after suspending. Interestingly, I can move the Ethernet adapter to the remaining USB-C port and it works correctly. Moving it back afterwards, it still does not work. Please let me know if there is anything more I can do to help. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aaron-work 35648 F pulseaudio /dev/snd/controlC0: aaron-work 35648 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 10:36:09 2022 InstallationDate: Installed on 2022-04-24 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:br1.12:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:sku07E6: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970392 Title: 22.04 USB devices do not work after sleep on Dell XPS 13 9370 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970185] Re: 20.04 does not remember preferred bluetooth headset microphone
** Attachment added: "Headset back on, output has gone back to the headset but microphone has not" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+attachment/5583423/+files/Screenshot%20from%202022-04-25%2009-43-46.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970185 Title: 20.04 does not remember preferred bluetooth headset microphone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970185] Re: 20.04 does not remember preferred bluetooth headset microphone
** Attachment added: "Headset turned off, input and output revert to internal ones" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+attachment/5583422/+files/Screenshot%20from%202022-04-25%2009-43-27.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970185 Title: 20.04 does not remember preferred bluetooth headset microphone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970185] [NEW] 20.04 does not remember preferred bluetooth headset microphone
Public bug reported: In Gnome's sound settings, it takes a sensible approach for my Bluetooth headset speaker: 1) I set it as my preferred audio Output Device 2) I turn the headset off and it disappears, reverting to the built in speakers 3) I turn the headset on again and it switches back to using the Bluetooth headset speaker This sensible approach is not taken for the microphone. The same flow for the microphone is: 1) Set the headset microphone as the default 2) Turn the headset off and it reverts to the internal microphone 3) Turn the headset back on and it stays as the internal microphone I have attached screenshots in case they help explain. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 09:44:42 2022 InstallationDate: Installed on 2022-04-24 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Headset on, headset mic and speaker set as input and output devices" https://bugs.launchpad.net/bugs/1970185/+attachment/5583417/+files/Screenshot%20from%202022-04-25%2009-42-41.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970185 Title: 20.04 does not remember preferred bluetooth headset microphone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949215] Re: Launching Pitivi repeatedly crashes Wayland user session and takes me back to login screen
I normally use Wayland. I just tested this using Xorg instead and it is working fine. Back to Wayland and it crashes. Back to Xorg and it is fine. ** Summary changed: - Launching Pitivi repeatedly crashes user session and takes me back to login screen + Launching Pitivi repeatedly crashes Wayland user session and takes me back to login screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949215 Title: Launching Pitivi repeatedly crashes Wayland user session and takes me back to login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1949215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949215] Re: Launching Pitivi repeatedly crashes user session and takes me back to login screen
It seems to also be doing something to my sound. I use a Plantronics headset (bluetooth, but with a dongle so it looks on the system like an analogue in and analogue out). When pitivi crashes and logs me out, my headset no longer works once I log back in. Switching the sound settings to use the headset input/output again and restarting seems to fix it. Just adding this in case it helps narrow down the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949215 Title: Launching Pitivi repeatedly crashes user session and takes me back to login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1949215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949215] [NEW] Launching Pitivi repeatedly crashes user session and takes me back to login screen
Public bug reported: I was using Pitivi without any issues and created a video. Now, opening Pitivi immediately crashes my user session and takes me back to the login screen. Ubuntu 20.04 with Pitivi from the archive -- hopefully all that is in the attached logs, but let me know if anything else would help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pitivi 0.999-2 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 16:54:12 2021 InstallationDate: Installed on 2020-05-03 (543 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pitivi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pitivi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949215 Title: Launching Pitivi repeatedly crashes user session and takes me back to login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1949215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938867] Re: Logitech K400R keyboard not entering text into input fields on Raspberry Pi 4
Ah interesting, thanks Daniel. I did not realise Raspberry Pis were doing Wayland by default. Yes, it works as expected in xorg, but not in Wayland. It's a Raspberry Pi 4 Model B - 8GB, in case that was not clear from my logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938867 Title: Logitech K400R keyboard not entering text into input fields on Raspberry Pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1938867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938867] [NEW] Keyboard not entering text into input fields
Public bug reported: I am running Hirsuite on a Raspberry Pi 4. My main keyboard for this (TV) machine is a wireless Logitech K400r combined keyboard/trackpad. When I first installed, I do not think there were any issues with the keyboard. When I did updates, my keyboard half-stopped working. It is very odd -- the keyboard is obviously working, as I can enter in my password on the lock screen or press Ctrl+Alt t for a terminal, but then I cannot enter anything into the terminal, Firefox input fields or anything else. Even more strangely, when I attach a second USB keyboard, both that new keyboard and my K400r work perfectly.When I unplug the USB keyboard, it stops working again. I'm not sure where this problem is, but: $ apt policy xserver-xorg-input-all xserver-xorg-input-all: Installed: 1:7.7+22ubuntu1 Please let me know if I can provide anything further to help diagnose this. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xserver-xorg-input-all 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-1015.16-raspi 5.11.22 Uname: Linux 5.11.0-1015-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 4 08:46:44 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1280x720M@60 smsc95xx.macaddr=E4:5F:01:48:E1:03 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image hirsute raspi-image ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938867 Title: Keyboard not entering text into input fields To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1938867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929032] Re: USB devices attached to USB-C Monitor do not work on resume from suspend to RAM
sudo lspci -vt ** Attachment added: "sudo lspci -vt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929032/+attachment/5499761/+files/20210524_lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929032 Title: USB devices attached to USB-C Monitor do not work on resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929032] Re: USB devices attached to USB-C Monitor do not work on resume from suspend to RAM
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929032/+attachment/5499759/+files/20210524_dmesg_log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929032 Title: USB devices attached to USB-C Monitor do not work on resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929032] Re: USB devices attached to USB-C Monitor do not work on resume from suspend to RAM
sudo lspci -vvv ** Attachment added: "sudo lspci -vvv" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929032/+attachment/5499760/+files/20210524_lspci-vvv.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929032 Title: USB devices attached to USB-C Monitor do not work on resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929032] Re: USB devices attached to USB-C Monitor do not work on resume from suspend to RAM
** Description changed: Hello, I have a certified Dell XPS 13 9370 that had Ubuntu pre-installed, though I have since installed normal 20.04 on it. I have my mouse, keyboard and headset dongle plugged in via my USB-C monitor. This works well. - Every evening, I suspend to RAM (note that I changed this from the - default instant suspend thing to proper suspend to RAM, as it was - draining battery terribly Bug #1808957 ) + Every evening, I suspend, which looks like it is in s2idle mode: $ sudo cat /sys/power/mem_sleep [s2idle] deep When I resume from sleep in the morning, the USB mouse, keyboard and headset dongle nearly never (but do occasionally) work. The lights on the dongle and mouse are not turned on. It is really annoying, as it means I have to keep re-suspending or pulling the cables out and in again until it finally starts working again or I shut everything down and restart. Any help would be appreciated. Please let me know if any further information would be helpful ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 20 08:51:17 2021 InstallationDate: Installed on 2020-05-03 (381 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929032 Title: USB devices attached to USB-C Monitor do not work on resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929032] [NEW] USB devices attached to USB-C Monitor do not work on resume from suspend to RAM
Public bug reported: Hello, I have a certified Dell XPS 13 9370 that had Ubuntu pre-installed, though I have since installed normal 20.04 on it. I have my mouse, keyboard and headset dongle plugged in via my USB-C monitor. This works well. Every evening, I suspend to RAM (note that I changed this from the default instant suspend thing to proper suspend to RAM, as it was draining battery terribly Bug #1808957 ) $ sudo cat /sys/power/mem_sleep [s2idle] deep When I resume from sleep in the morning, the USB mouse, keyboard and headset dongle nearly never (but do occasionally) work. The lights on the dongle and mouse are not turned on. It is really annoying, as it means I have to keep re-suspending or pulling the cables out and in again until it finally starts working again or I shut everything down and restart. Any help would be appreciated. Please let me know if any further information would be helpful ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-53-generic 5.8.0-53.60~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 20 08:51:17 2021 InstallationDate: Installed on 2020-05-03 (381 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929032 Title: USB devices attached to USB-C Monitor do not work on resume from suspend to RAM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1929032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892379] Re: Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling
** Attachment added: "Playback on 200% screen" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403153/+files/Screenshot%20from%202020-08-20%2015-54-40.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892379 Title: Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892379] Re: Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling
** Attachment added: "Display Settings screenshot 2" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403155/+files/Screenshot%20from%202020-08-20%2015-56-01.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892379 Title: Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892379] Re: Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling
** Attachment added: "Display Settings screenshot 1" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+attachment/5403154/+files/Screenshot%20from%202020-08-20%2015-55-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/1892379 Title: Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892379] [NEW] Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling
Public bug reported: I am using Ubuntu Focal Fossa with Wayland and two screens. Display 1 is a 3840 x 2160 screen at 200% scaling Display 2 is a 1920x1200 at 100% scaling Fractional Scaling is on. Display 2 is my Primary Display. When I play a video on Display 2, everything works as expected. When I play a video on Display 1 (whether I drag it there or it is there all along) then it plays taking up only the top-left corner of the window. May be related to: https://bugzilla.redhat.com/show_bug.cgi?id=1529008 https://gitlab.gnome.org/GNOME/totem/-/issues/271 https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/252 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 15:45:13 2020 InstallationDate: Installed on 2020-05-03 (108 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Attachment added: "Video playback on 100% screen" https://bugs.launchpad.net/bugs/1892379/+attachment/5403147/+files/Screenshot%20from%202020-08-20%2015-54-27.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892379 Title: Totem plays video scaled down on HiDPI screen on Wayland with multiple monitors at different fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1892379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function
Hello all, Apologies, I missed these recent messages. For background, the error UnicodeDecodeError just means that a non-ASCII character is hitting a piece of code that was not designed to handle it. That is not surprising -- prior to the 0.8 series, very little of the code was designed for non-ASCII characters. What that means is that you may be seeing a UnicodeDecodeError even though this bug is fixed, because somewhere else in the code needs fixing. Victor Douglas (jhngalt): This is an interesting error and thank you very much for following our instructions on testing the snap and giving the relevant details. Can you please test with the latest stable duplicity snap and, if you still have a problem, report the bug in our new tracker (https://gitlab.com/duplicity/duplicity/-/issues )? Note that "snap run duplicity" does not actually do anything without arguments (even working correctly it gives: Command line error: Expected 2 args, got 0 Enter 'duplicity --help' for help screen.), but it still should not be giving an error like that. It looks as though the error was related to non-ASCII in your temporary directory name not being handled correctly. Martin Theiner (mathesubu1) and BlueT - Matthew Lien - 練喆明 (bluet) -- you are both using an old (pre 0.8 series) version of duplicity/deja dup. Please uninstall the system version (e.g. "sudo apt-get purge duplicity") and install the stable snap (e.g. "sudo snap install duplicity —classic") and test again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770929 Title: Duplicity fails with UnicodeDecodeError in uexc function To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1770929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879742] [NEW] When using Google Meet on Firefox, delay sending sound from microphone
Public bug reported: When using Google Meet in Firefox (Ubuntu 20.04, 76.0.1 (64-bit)), for the first 5-10 seconds of the meeting, nobody can hear anything that I am saying. After that, I have no issues. I also have no issues joining with Chromium. The sound indicator on my end (the little green bars that flash when you are talking) start immediately, but nobody on the call hears anything from me. The only info I could find from Googling was somebody else talking about a similar problem: https://www.reddit.com/r/firefox/comments/9aoae0/google_meet_sound_delayed_on_linux_at_least/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 76.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 1813 F pulseaudio BuildID: 20200507114007 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed May 20 17:05:20 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-05-03 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.14 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:738 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=76.0.1/20200507114007 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879742 Title: When using Google Meet on Firefox, delay sending sound from microphone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1879742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877038] Re: Firefox seems to lack FIDO2 support with Yubikeys
Is this related to: https://bugzilla.mozilla.org/show_bug.cgi?id=1530370 ? If so, in the duplicate bug (https://bugzilla.mozilla.org/show_bug.cgi?id=1619850 ) somebody said "This is a 2020 goal." ** Package changed: evolution (Ubuntu) => firefox (Ubuntu) ** Bug watch added: Mozilla Bugzilla #1530370 https://bugzilla.mozilla.org/show_bug.cgi?id=1530370 ** Bug watch added: Mozilla Bugzilla #1619850 https://bugzilla.mozilla.org/show_bug.cgi?id=1619850 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877038 Title: Firefox seems to lack FIDO2 support with Yubikeys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1877038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function
All, This should be fixed in 0.8.00, which has now been released. This is the first 0.8-series release, so expect issues and test it out on data you can afford to lose (if it comes to that). I have now packaged up this version as a snap. You can install it by typing: snap install duplicity --classic --beta Please uninstall your current version of duplicity to ensure you are using the snap instead of one from apt etc. (This will work out of the box on nearly all versions of Ubuntu. If you use a different distro and have never installed snaps before, visit this page: https://docs.snapcraft.io/installing-snapd ) This includes the latest duplicity and all dependencies wrapped up in a self-contained bundle. You should not need to install anything else for this to work (including for all backends). If you do test this, it would be very helpful if you could please comment here, even if the only feedback is that all worked as expected. If you are giving any feedback, please also give the output of: which duplicity and snap list | grep duplicity and let me know which backends you used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770929 Title: Duplicity fails with UnicodeDecodeError in uexc function To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1770929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function
All, to clarify the current position, this is fixed in the 0.8 series, but I set out the steps to test the fix in comment #15 and was waiting on testing feedback before merging the patch back into the 0.7 series. Nobody gave me any testing feedback. It is therefore not yet fixed in the 0.7 series. It looks as though Ubuntu has separately patched this in Disco only (comment #19). So it will not work in Bionic or Xenial. We are now so close to a 0.8 release that I am inclined to wait for that and encourage affected users to move straight to that, rather than risk breaking people who are sticking to the 0.7 series. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770929 Title: Duplicity fails with UnicodeDecodeError in uexc function To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1770929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440372] Re: please port duplicity to Python3
@Sebastian, Kenneth is planning to release a 0.8 version very soon. Note that I have wound the Python 3 blueprint completion back a step, as I have realised that there are some backend dependencies (e.g. pyrax) that do not work on Python 3. I believe deja dup only uses a subset of the backends anyway, so what has already been done may be sufficient once a 0.8-series release is out the door. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440372 Title: please port duplicity to Python3 To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1440372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826550] Re: Fractional scaling options do not appear with multiple monitors
** Attachment added: "Screenshot with external monitor connected. Only whole number scaling available." https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826550/+attachment/5259303/+files/Screenshot%20from%202019-04-26%2014-32-06.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826550 Title: Fractional scaling options do not appear with multiple monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826550] [NEW] Fractional scaling options do not appear with multiple monitors
Public bug reported: Using 19.04 disco with Wayland. I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor. I have enabled the experimental fractional scaling support. When no external monitor is connected, the fractional scaling options are displayed as expected. When the external monitor is connected, only the old whole number scaling options are displayed. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 14:32:55 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-04 (234 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages wayland-session ** Attachment added: "With no external monitor. Fractional scaling options shown." https://bugs.launchpad.net/bugs/1826550/+attachment/5259299/+files/Screenshot%20from%202019-04-26%2014-32-37.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826550 Title: Fractional scaling options do not appear with multiple monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826547] [NEW] [Wayland] Display change "Revert Settings" window uses primary screen scaling factor
Public bug reported: Using 19.04 disco with Wayland. I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor. I have the laptop screen set to 200% and the external screen set to 100%. If I set the primary display to the built-in display but have the display settings window open on the external screen, then when I change the scaling factor of the built-in display to e.g. 300% and click Apply, the "Do you want to keep these settings" confirmation window appears on the external screen, scaled by 300%. If the external monitor is the primary display, it is always scaled normally at 100%. Conversely, if the external monitor is set as the primary display, but the settings window is on the built-in display, then when I change the scaling factor of the external monitor to 100%, then this "Do you want to keep these settings" dialog appears incorrectly scaled at 100% instead of 200%. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 14:16:23 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-04 (234 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826547 Title: [Wayland] Display change "Revert Settings" window uses primary screen scaling factor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1826547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826543] [NEW] [Wayland] Support multiple monitors with different scaling factors
Public bug reported: Running 19.04 Disco with Wayland Version 64ubuntu7 I have a HiDPI laptop screen (XPS13) and a normal DPI external monitor. I have the laptop screen set to 200% and the external screen set to 100%. When running the display solely on my built-in monitor, the dock is correctly scaled to 200%. When running the display is running solely on the external monitor, the dock is scaled to 100%. When running both monitors at the same time, the scaling factor used for the docks on both monitors is the scaling factor of the primary monitor: so if that is the external screen is primary then the laptop screen version of the dock is tiny; and if the built-in screen is primary then the external monitor dock is huge. I would expect the dock scaling factor to always match the scaling factor of the screen that the dock is displayed on. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [Wayland] Scale the dock based on the scaling factor for that monitor + [Wayland] Support multiple monitors with different scaling factors -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826543 Title: [Wayland] Support multiple monitors with different scaling factors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1826543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function
The 0.8-series was affected by this (as I mentioned above, fixing the underlying problem avoids this error and a number of these have been fixed, so it is harder to trigger). I have just proposed a fix for it be merged into the 0.8-series: https://code.launchpad.net/~aaron-whitehouse/duplicity/08-uexc-fix I would still appreciate any feedback on the 0.7-series branch above. I am more nervous about making changes in our stable branch without feedback. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770929 Title: Duplicity fails with UnicodeDecodeError in uexc function To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1770929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440372] Re: please port duplicity to Python3
Marking this as Fix Committed, as we have Python 3 compatible code in 0.8-series with all tests also being run against this environment. We have not yet put out a 0.8 release, though. See https://blueprints.launchpad.net/duplicity/+spec/python3 ** Changed in: duplicity Importance: Undecided => High ** Changed in: duplicity Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440372 Title: please port duplicity to Python3 To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1440372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770929] Re: Duplicity fails with UnicodeDecodeError in uexc function
Thank you everybody for your bug reports and comments.
I believe that this bug is already fixed in the 0.8-series, but we have
not yet released a package for this.
The code triggering this is used when there is an exception/error
message containing a non-ASCII character (for example a filename), so
this is sometimes 'fixed' by fixing the underlying problem. This is why
some commenters say the problem went away when they resolved permissions
issues. I do not know what has changed that is causing this to break for
people it did not break for previously.
The reality is that version 0.7 and below were never actually written to
accommodate non-ASCII characters and the fact it worked at all was
largely luck. The 0.8 series does add proper support for non-ASCII, with
the internals converted to Unicode and Python 3 support.
Many thanks to Pete Zaitcev (zaitcev) in Bug #1797928 for proposing a
patch for this, which I had overlooked.
I have applied this in the branch here: lp:~aaron-
whitehouse/duplicity/07-uexc-fix
It would be helpful if you can please test to see if this fixes your problem as
follows:
1. Create a new destination directory to test with.
2. Test that duplicity fails as you have reported when using this destination.
3. Pull down a copy of the branch with the fix:
bzr branch lp:~aaron-whitehouse/duplicity/07-uexc-fix dup_patched
4. cd dup_patched/duplicity
5. run ./compilec.py
6. change directory back to wherever you were running duplicity from before
5. Test with the patched duplicity:
PYTHONPATH=[full path/]dup_patched [full path/]dup_patched/bin/duplicity [all
of your options/arguments]
Please let me know how you get on.
== Simple illustration of failure ==
A simple example triggering this bug is to create a couple of empty
directories, say "source1" and "dest".
Then try:
duplicity --exclude=bänana source1/ file://dest/
This should give a FilePrefixError (hideous in version 0.7 and much more
informative in 0.8), but instead says:
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1611, in
if "Forced assertion for testing" in util.uexc(e):
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 1: ordinal
not in range(128)
** Branch linked: lp:~aaron-whitehouse/duplicity/07-uexc-fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770929
Title:
Duplicity fails with UnicodeDecodeError in uexc function
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1770929/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770929] Re: backup fails with UnicodeDecodeError in uexc function
** Summary changed: - backup fails with UnicodeDecodeError + backup fails with UnicodeDecodeError in uexc function ** Summary changed: - backup fails with UnicodeDecodeError in uexc function + Duplicity fails with UnicodeDecodeError in uexc function -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770929 Title: Duplicity fails with UnicodeDecodeError in uexc function To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1770929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
Using the firmware from Comment #5 above stopped the wireless and my my Bluetooth mouse from working, so I have reverted it to the standard Ubuntu version. sudo lspci -vvv -s 02:00.0 gives: 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1807974 Title: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
Correct. Since I have been using Deep instead of S2Idle I have seen the issue less -- though it has only been a couple of days as I was not using this machine over the holidays. Even when it does break, Deep suspending and resuming the machine brings the wireless back up and working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807974 Title: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
Done, thanks Kai-Heng. How can I check I'm using the new versions? $ dmesg | grep ath10k [ 15.152725] ath10k_pci :02:00.0: enabling device ( -> 0002) [ 15.154816] ath10k_pci :02:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [ 15.436782] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:143a [ 15.436784] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [ 15.437201] ath10k_pci :02:00.0: firmware ver RM.4.4.1.c2-00057-QCARMSWP-1 api 6 features wowlan,ignore-otp,no-4addr-pad,raw-mode crc32 e061250a [ 15.502002] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 20d869c3 [ 16.081468] ath10k_pci :02:00.0: Unknown eventid: 118809 [ 16.084029] ath10k_pci :02:00.0: htt-ver 3.56 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 16.176519] ath10k_pci :02:00.0 wlp2s0: renamed from wlan0 [ 19.218623] ath10k_pci :02:00.0: Unknown eventid: 118809 I will let you know how I get on. Even before loading the new firmware I am seeing this issue far less frequently (only twice so far today) since I changed s2idle to deep sleep (Bug #1808957), so I suspect it does relate to idle/power saving. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807974 Title: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep
I'm marking this as incomplete for now until I can provide more information on relative power usage, things broken in modern standby/s2idle etc. If we can get the power usage materially similar to deep sleep but with an instant-on experience etc (and everything else works as expected) then that seems the ideal. I will put together some statistics on relative power usage. I will keep it open, though, as if there is a substantial delta in power use that cannot be quickly fixed, I think there is at least an argument to default to deep sleep until those fixes are made (certainly I am much happier now I have made the change). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep
More background information on 'Modern Standby' on Linux here: https://lwn.net/Articles/580451/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep
Having looked into this in more detail, it sounds as though this is the intended behaviour for new laptops that declare ACPI_FADT_LOW_POWER_S0: https://patchwork.kernel.org/patch/9433419/ This appears related to: https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/behavior-differences-between-s3-and-modern-standby If that is the case and this laptop is supposed to be able to do S2I that is low power but quicker to suspend and resume, then I guess I can understand Kai-Heng's comment (though the suspend/resume process is < few seconds for me with S3). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
Normally (maybe always?) it is when the network is idle. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807974 Title: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808957] [NEW] Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep
Public bug reported: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 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-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807974] [NEW] Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic
Public bug reported:
I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
Cosmic. A handful of times per day, my wireless stops working ("?"
appears in the icon in Network Manager). Turning wireless off and then
on again, or suspending and waking the machine up, makes the wireless
work again.
dmesg output is as follows:
$ dmesg | grep ath10k
[ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid
6317c652-4817-4fdd-b6d7-c7b8336e493f)
[ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id
0x00340aff sub 1a56:143a
[ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs
0 testmode 0
[ 6646.270369] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp
max-sta 32 raw 0 hwcrypto 1
[ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
[ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800 29 29 106 107
[ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00 20 19 18 19
[ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000 8 8 10 8
[ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
[ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 6 6
[ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
[ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
[ 6647.239340] ath10k_pci :02:00.0: device successfully recovered
[17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid
03393f2f-0ce1-4017-b711-40dd14f2ec11)
[17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 chip_id
0x00340aff sub 1a56:143a
[17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs
0 testmode 0
[17641.848065] ath10k_pci :02:00.0: firmware ver
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32
20d869c3
[17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal otp
max-sta 32 raw 0 hwcrypto 1
[17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for
firmware address 4: -16
[17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
[17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
[17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400 14 14 3 3
[17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800 6 6 243 244
[17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00 53 52 51 52
[17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000 5 5 7 5
[17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
[17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800 0 0 64 0
[17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00 0 0 30 30
[17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000 0 1 0 1
[17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address:
-28
[17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
[17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
[17642.835601] ath10k_pci :02:00.0: device successfully recovered
[17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
[17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118
I do not recall having any wireless issues before I upgraded (when this
machine was running Bionic).
Bug #1730331 - ath10k_pci: firmware crashed!
Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
could be related, but appear to be related to earlier releases, whereas my
issue has appeared/become much worse on Cosmic.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-11-generic 4.18.0-11.12
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: aaron-work 3476 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 11 14:21:44 2018
EcryptfsInUse: Yes
HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1
InstallationDate: Installed on 2018-09-04 (98 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
[Bug 1730331] Re: ath10k_pci: firmware crashed!
See also Bug #1627474 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730331 Title: ath10k_pci: firmware crashed! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627474] Re: ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a)
See also Bug #1730331 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627474 Title: ath10k_pci :03:00.0: firmware crashed! (uuid n/a) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1627474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731341] Re: Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)"
Anything that I can do to help get this fix into the Ubuntu package? I cannot import photos, which is enough of a problem that I'm considering downgrading to the earlier release -- but happy to help try to fix 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/1731341 Title: Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gphoto2/+bug/1731341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731341] Re: Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)"
Marcus has said in the upstream bug: "I released 2.5.16 some weeks ago. the commit fixing this issue for backporting is 472a9461b457b4d08ecf10a93bb7f1efdc2124c0 " It would be excellent if this could please make its way into Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731341 Title: Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gphoto2/+bug/1731341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731341] Re: Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)"
** Also affects: gphoto2 (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/1731341 Title: Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gphoto2/+bug/1731341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731341] Re: Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)"
I would say this is a duplicate of Bug #910964, except that bug hasn't had any action since 2013 and this only just stopped working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731341 Title: Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1731341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731341] Re: Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)"
Looks like it is this: https://sourceforge.net/p/gphoto/bugs/1032/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731341 Title: Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1731341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731341] Re: Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)"
$ gphoto2 -T
*** Error ***
An error occurred in the io-library ('Unspecified error'): No error description
available
*** Error (-1: 'Unspecified error') ***
For debugging messages, please use the --debug option.
Debugging messages may help finding a solution to your problem.
If you intend to send any error or debug messages to the gphoto
developer mailing list , please run
gphoto2 as follows:
env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt -T
Please make sure there is sufficient quoting around the arguments.
===
$ env LANG=C gphoto2 --debug --debug-logfile=my-logfile.txt -T
*** Error ***
An error occurred in the io-library ('Unspecified error'): No error description
available
*** Error (-1: 'Unspecified error') ***
** Attachment added: "my-logfile"
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1731341/+attachment/5007138/+files/my-logfile.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731341
Title:
Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the
camera: Unspecified error (-1)"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1731341/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731341] [NEW] Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)"
Public bug reported: I have a Fujifilm X-T10. This worked perfectly in Shotwell in 17.04. Since upgrading to 17.10, I receive an error whenever I try to import photos: Unable to fetch previews from the camera: Unspecified error (-1) lsusb gives: Bus 001 Device 010: ID 04cb:02c8 Fuji Photo Film Co., Ltd dmesg gives: [ 585.129167] usb 1-2: new high-speed USB device number 10 using xhci_hcd [ 585.269979] usb 1-2: New USB device found, idVendor=04cb, idProduct=02c8 [ 585.269980] usb 1-2: New USB device strings: Mfr=0, Product=2, SerialNumber=3 [ 585.269981] usb 1-2: Product: USB PTP Camera [ 585.269981] usb 1-2: SerialNumber: 59353130303416092266F93011BFE6 This looks like the same issue reported in Ask Ubuntu (with no answer) here: https://askubuntu.com/questions/972613/usb-ptp-camera-no-longer-working-after-upgrade-to-17-10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: shotwell 0.26.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 9 21:36:30 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-03 (494 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: shotwell UpgradeStatus: Upgraded to artful on 2017-10-29 (11 days ago) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731341 Title: Fujifilm X-T10 regression on 17.10: "Unable to fetch previews from the camera: Unspecified error (-1)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1731341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651396] Re: Backup fails every time after one incremental file is possibly corrupted
Have you tried to verify your backup or do a new full backup? > Can someone recommend a better backup software for personal use? http://lmgtfy.com/?q=personal+backup+software+linux There is a reason, though, that Deja Dup (which you are already using) is the default in Ubuntu -- it is a pretty good balance of ease of use and reliability. Kind regards, Aaron -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651396 Title: Backup fails every time after one incremental file is possibly corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1651396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled
Jonathan, Given the latest version of xfce-settings (4.12.1) was easy to install and fixed all of my issues (see comment #130 above), it would be interesting to know whether this also fixed your problem. Kind regards, Aaron -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308105 Title: Xfce resets TV mode to NULL when power cycled To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1308105] Re: Xfce resets TV mode to NULL when power cycled
I have an ASUS Z170M-Plus Mobo with an Intel Core i3-6100T, Intel HD 530 graphics and a Samsung TV connected through HDMI, running Mythbuntu 16.04. I had the issue that when I turned the TV off and then back on again, the TV would say "No Signal" and I would have to run $ sudo service lightdm restart to get it to work again. Based on Alexandre's comment #128, I installed xfce-settings 4.12.1 from here: https://packages.debian.org/stretch/amd64/xfce4-settings/download http://ftp.uk.debian.org/debian/pool/main/x/xfce4-settings/xfce4-settings_4.12.1-1_amd64.deb and installed it on my Mythbuntu 16.04 installation. To my surprise, I didn't have any dependency issues, it all applied without problems and now the problem seems fixed! I can turn the TV off and on again and the picture comes back as expected. Great work all in getting this sorted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308105 Title: Xfce resets TV mode to NULL when power cycled To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1413665] Re: Bad Request - Bad bot, go away! Request aborted.
Yes, not fixed for me either. * Ubuntu 16.04 x64 * Firefox 47.0 * Keefox 1.6.0 Trying to log into help.ubuntu.com, I get the " Bad Request Bad bot, go away! Request aborted. " message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1413665 Title: Bad Request - Bad bot, go away! Request aborted. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-identity-provider/+bug/1413665/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1266003] Re: unity visible with wine fullscreen applications
Duplicate of Bug #1388648? (This one is actually older, but that one is higher priority and has slightly more information.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1266003 Title: unity visible with wine fullscreen applications To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1266003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1388648] Re: Wine shows the Unity Launcher when an application runs in full-screen with a resolution different from the native
Also (unsurprisingly) an issue in Crossover (15.2 on Ubuntu 16.04), for example using the default crosstie for Age of Empires 2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1388648 Title: Wine shows the Unity Launcher when an application runs in full-screen with a resolution different from the native To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1388648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329133] Re: Error message about .dbus directory shows up after backup even though the directory is excluded.
*** This bug is a duplicate of bug 1313034 *** https://bugs.launchpad.net/bugs/1313034 ** This bug has been marked a duplicate of bug 1313034 Deja-dup reports it couldn't backup ~/.cache/dconf and ~/.gvfs even though it's not supposed to try to (also, ~/.dbus) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329133 Title: Error message about .dbus directory shows up after backup even though the directory is excluded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1329133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450755] Re: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi)
Thanks Christopher, Do you want me to do this with the latest mainline kernel, rather than the Ubuntu 15.10 one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450755 Title: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450755] Re: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi)
For comparison, on Windows 7 (machine in same spot) Up to 54Mbps >iperf -c 192.168.0.102 Client connecting to 192.168.0.102, TCP port 5001 TCP window size: 63.0 KByte (default) [ 3] local 192.168.0.2 port 49809 connected with 192.168.0.102 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 26.8 MBytes 22.3 Mbits/sec Changed to Up to 144Mbps >iperf -c 192.168.0.102 Client connecting to 192.168.0.102, TCP port 5001 TCP window size: 63.0 KByte (default) [ 3] local 192.168.0.2 port 49828 connected with 192.168.0.102 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 66.2 MBytes 55.4 Mbits/sec Changed to Up to 300Mbps >iperf -c 192.168.0.102 Client connecting to 192.168.0.102, TCP port 5001 TCP window size: 63.0 KByte (default) [ 3] local 192.168.0.2 port 49838 connected with 192.168.0.102 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 66.5 MBytes 55.7 Mbits/sec So, in summary: | Mainline 4.5rc5 | Windows 7 | Up to 54 Mbps | 20.9 Mbps |22.3 Mbps | Up to 144Mbps (best for wireless range)| 17.1 Mbps |55.4 Mbps | Up to 300Mbps (best for w/ performance) | 19.8 Mbps |55.7 Mbps | -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450755 Title: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450755] Re: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi)
Ah right, thanks Christopher. Sorry, I thought you were meaning on the Ubuntu side. I've now done that (on the latest mainline) and there doesn't seem to be a significant variation. $ uname -r 4.5.0-040500rc5-generic Wireless mode was 'Up to 144Mbps (best for wireless range)' $ iperf -c 192.168.0.102 Client connecting to 192.168.0.102, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 192.168.0.2 port 56136 connected with 192.168.0.102 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.2 sec 20.8 MBytes 17.1 Mbits/sec Changed to 'Up to 300Mbps (best for wireless performance)' $ iperf -c 192.168.0.102 Client connecting to 192.168.0.102, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 192.168.0.2 port 56200 connected with 192.168.0.102 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 23.9 MBytes 19.8 Mbits/sec Changed to 'Up to 54Mbps (best for wireless compatibility with older devices)' $ iperf -c 192.168.0.102 Client connecting to 192.168.0.102, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 192.168.0.2 port 56222 connected with 192.168.0.102 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 25.0 MBytes 20.9 Mbits/sec -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450755 Title: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450755] Re: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi)
This issue still persists in 15.10. $ iperf -s Server listening on TCP port 5001 TCP window size: 85.3 KByte (default) [ 4] local 192.168.0.102 port 5001 connected with 192.168.0.2 port 49287 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.0 sec 83.9 MBytes 70.2 Mbits/sec [ 5] local 192.168.0.102 port 5001 connected with 192.168.0.2 port 49294 [ 5] 0.0-10.0 sec 78.4 MBytes 65.6 Mbits/sec [ 4] local 192.168.0.102 port 5001 connected with 192.168.0.2 port 49296 [ 4] 0.0-10.0 sec 84.5 MBytes 70.8 Mbits/sec [ 5] local 192.168.0.102 port 5001 connected with 192.168.0.2 port 55344 [ 5] 0.0-10.0 sec 14.5 MBytes 12.2 Mbits/sec [ 4] local 192.168.0.102 port 5001 connected with 192.168.0.2 port 55346 [ 4] 0.0-10.2 sec 14.4 MBytes 11.8 Mbits/sec [ 5] local 192.168.0.102 port 5001 connected with 192.168.0.2 port 55348 [ 5] 0.0-10.2 sec 11.2 MBytes 9.27 Mbits/sec The first three results are on Windows 7, second three are on Ubuntu 15.10. Same laptop in the same place. Kernel version is 4.2.0-25-generic I can install the mainline kernel again to try to help. You asked whether switching 802.11 type made any difference on the mainline kernel - what is the easiest way to switch between these 802.11 types? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450755 Title: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482915] [NEW] Merge conflict information unreadable (white text on light yellow)
Public bug reported: I really like using Bazaar Explorer, but I have issues every time that I try to use the merge functionality. The text that comes up if there is a conflict is white text on a yellow background and I can never see what it is asking me. I've attached an example screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bzr-explorer 1.3.0-2 Uname: Linux 4.1.0-040100rc6-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 8 22:24:51 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-26 (834 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: bzr-explorer UpgradeStatus: Upgraded to vivid on 2015-04-25 (105 days ago) ** Affects: bzr-explorer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Attachment added: Screenshot from 2015-08-08 22:24:13.png https://bugs.launchpad.net/bugs/1482915/+attachment/4441492/+files/Screenshot%20from%202015-08-08%2022%3A24%3A13.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482915 Title: Merge conflict information unreadable (white text on light yellow) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzr-explorer/+bug/1482915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450755] Re: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi)
Updated to latest upstream again. $ uname -r 4.1.0-040100rc6-generic $ iwconfig virbr0-nic no wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11bgn ESSID:VM851079-2G Mode:Managed Frequency:2.462 GHz Access Point: 10:0D:7F:18:C4:80 Bit Rate=65 Mb/s Tx-Power=16 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=70/70 Signal level=-30 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:77 Missed beacon:0 virbr0no wireless extensions. lono wireless extensions. = $ iperf -c 192.168.0.102 Client connecting to 192.168.0.102, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 192.168.0.3 port 49106 connected with 192.168.0.102 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 23.1 MBytes 19.2 Mbits/sec = Latest router info: Information Cable Modem EuroDOCSIS 3.0 Compliant Serial Number 3BW132UG04977 Boot Code Version PSPU-Boot 1.0.20.1356 Software VersionV1.01.29 Hardware Version3.11 ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450755 Title: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450755] Re: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi)
No, it doesn't seem to. = $ iwconfig virbr0-nic no wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11bgn ESSID:VM851079-2G Mode:Managed Frequency:2.462 GHz Access Point: 10:0D:7F:18:C4:80 Bit Rate=130 Mb/s Tx-Power=16 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=70/70 Signal level=-30 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:56 Missed beacon:0 virbr0no wireless extensions. lono wireless extensions. == $ iperf -c 192.168.0.102 Client connecting to 192.168.0.102, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 192.168.0.3 port 39692 connected with 192.168.0.102 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 21.2 MBytes 17.6 Mbits/sec $ sudo iwconfig wlan0 power off [sudo] password for : $ iwconfig virbr0-nic no wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11bgn ESSID:VM851079-2G Mode:Managed Frequency:2.462 GHz Access Point: 10:0D:7F:18:C4:80 Bit Rate=130 Mb/s Tx-Power=16 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=70/70 Signal level=-30 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:107 Missed beacon:0 virbr0no wireless extensions. lono wireless extensions. === $ iperf -c 192.168.0.102 Client connecting to 192.168.0.102, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 192.168.0.3 port 39693 connected with 192.168.0.102 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 13.1 MBytes 10.9 Mbits/sec [Tried again immediately afterwards, without changing anything] $ iperf -c 192.168.0.102 Client connecting to 192.168.0.102, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 192.168.0.3 port 39694 connected with 192.168.0.102 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 27.4 MBytes 22.8 Mbits/sec ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450755 Title: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450755] Re: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi)
I don't think so, no. It's this: http://electronics360.globalspec.com/article/3410/netgear-super-hub-2-vmdg485-wireless-router-teardown which looks quite different to the pictures on the page that you linked to. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450755 Title: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450755] Re: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi)
It's a Virgin Media Superhub 2, which is a Netgear VMDG485: Information Cable Modem EuroDOCSIS 3.0 Compliant Serial Number 3BW132UG04977 Boot Code Version PSPU-Boot 1.0.20.1356 Software VersionV1.01.29 Hardware Version3.11 Please let me know if you need anything further. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450755 Title: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450755] Re: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi)
I have just tested this with the latest upstream kernel: $ iperf -c 192.168.0.102 Client connecting to 192.168.0.102, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 192.168.0.3 port 40963 connected with 192.168.0.102 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 19.5 MBytes 16.2 Mbits/sec $ uname -r 4.1.0-040100rc3-generic So it appears that the bug exists upstream. ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.1-rc3 ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450755 Title: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450755] Re: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi)
Updating the BIOS does not solve the issue (the speed actually reduced slightly). After updating the BIOS, this is the output: [ 3] local 192.168.0.3 port 49429 connected with 192.168.0.102 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 21.6 MBytes 18.0 Mbits/sec $ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date [sudo] password for [...]: A13 05/18/2013 ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450755 Title: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450755] [NEW] Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi)
Public bug reported: My Intel wireless card is significantly slower in Ubuntu than it is in Windows 7. According to iperf (with the laptop a couple of feet from the router and the server plugged into it): == Ubuntu 15.04 == [ 4] local 192.168.0.102 port 5001 connected with 192.168.0.3 port 43672 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.1 sec 23.2 MBytes 19.3 Mbits/sec == Windows 7 === [ 4] local 192.168.0.102 port 5001 connected with 192.168.0.3 port 49247 [ 4] 0.0-10.1 sec 98.4 MBytes 82.0 Mbits/sec Transfer rates for previous Ubuntu releases are about the same: -- 13.10: [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 22.6 MBytes 18.9 Mbits/sec -- 14.10 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 27.8 MBytes 23.1 Mbits/sec I have attached the output of Wireless Script, which should give all the necessary details about my setup. Any thoughts would be appreciated. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron 2193 F pulseaudio CurrentDesktop: Unity Date: Fri May 1 10:37:38 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-26 (734 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. Inspiron 5423 ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=UUID=e429a76e-75c0-44b9-90d4-a75ee21d98a2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-25 (5 days ago) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0RMVR3 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/03/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0RMVR3:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5423 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug vivid ** Attachment added: Output from Wireless Script https://bugs.launchpad.net/bugs/1450755/+attachment/4388959/+files/wireless-info.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450755 Title: Intel Wireless-N 2230 4x faster in Windows 7 than 15.04 (iwlwifi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1366551] Re: I am runing linuxMint 17 64bit. I have install all the cods for Acidrip does not exist
Hello William, This is more a request for advice at this stage, so I have converted your bug to a question. If there are any bugs or feature requests that become clear when people are answering your question, you could open a new bug for these at that stage. ** Changed in: mythtv (Ubuntu) Status: New = Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/mythtv/+question/254178 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1366551 Title: I am runing linuxMint 17 64bit. I have install all the cods for Acidrip does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1366551/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332223] Re: [Regression] TeVii dual DVB-S S480 (=2 x DVB-S2 S660) fails to lock on channels
Apologies all to waste your time. It turns out that, in moving my computer slightly to upgrade the OS, the inside of my aerial cable broke and this was a hardware issue. I realised when I rolled it back and the issue persisted. I have replaced the cable and all works fine now, thanks. ** Changed in: linux (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/1332223 Title: [Regression] TeVii dual DVB-S S480 (=2 x DVB-S2 S660) fails to lock on channels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1332223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1332223] [NEW] [Regression] TeVii dual DVB-S S480 (=2 x DVB-S2 S660) fails to lock on channels
Public bug reported: I was using the TeVii DVB-S2 S480 (which is a dual tuner equivalent to two DVB-S2 660 cards): http://www.linuxtv.org/wiki/index.php/TeVii_S480 in Mythbuntu 12.04 for a long time without issue. I have recently updated to 14.04 and it will no longer lock on channels, giving the dmesg error: [ 37.157002] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)... [ 37.207906] ds3000_firmware_ondemand: Waiting for firmware upload(2)... [ 40.269732] ds3000_firmware_ondemand: Waiting for firmware upload (dvb-fe-ds3000.fw)... [ 40.269806] ds3000_firmware_ondemand: Waiting for firmware upload(2)... I will roll back to 12.04 to check that it is all working fine without my touching hardware/aerials, but wanted to post this when it could capture all the logs etc. Potentially relevant other bugs: https://bbs.archlinux.org/viewtopic.php?pid=1351401 https://bugzilla.redhat.com/show_bug.cgi?id=963715 http://ubuntuforums.org/showthread.php?t=2219210 All the relevant dmesg seems to be: == [ 13.840086] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw' [ 13.840090] dw2102: start downloading DW210X firmware [ 14.144806] dvb-usb: found a 'TeVii S480.1 USB' in warm state. [ 14.145006] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 14.145037] DVB: registering new adapter (TeVii S480.1 USB) [ 14.145220] dvb-usb: MAC address: 28:28:28:28:28:28 [ 14.226805] type=1400 audit(1403197887.426:2): apparmor=STATUS operation=profile_load profile=unconfined name=/sbin/dhclient pid=516 comm=apparmor_parser [ 14.226815] type=1400 audit(1403197887.426:3): apparmor=STATUS operation=profile_load profile=unconfined name=/usr/lib/NetworkManager/nm-dhcp-client.action pid=516 comm=apparmor_parser [ 14.226820] type=1400 audit(1403197887.426:4): apparmor=STATUS operation=profile_load profile=unconfined name=/usr/lib/connman/scripts/dhclient-script pid=516 comm=apparmor_parser [ 14.227460] type=1400 audit(1403197887.426:5): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/NetworkManager/nm-dhcp-client.action pid=516 comm=apparmor_parser [ 14.227468] type=1400 audit(1403197887.426:6): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/connman/scripts/dhclient-script pid=516 comm=apparmor_parser [ 14.227812] type=1400 audit(1403197887.426:7): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/connman/scripts/dhclient-script pid=516 comm=apparmor_parser [ 14.251095] type=1400 audit(1403197887.450:8): apparmor=STATUS operation=profile_load profile=unconfined name=/usr/sbin/ntpd pid=602 comm=apparmor_parser [ 14.389246] Invalid probe, probably not a DS3000 [ 14.389268] dvb-usb: no frontend was attached by 'TeVii S480.1 USB' [ 14.389644] input: IR-receiver inside an USB DVB receiver as /devices/pci:00/:00:04.0/:02:00.1/usb3/3-1/input/input6 [ 14.389954] dvb-usb: schedule remote query interval to 150 msecs. [ 14.389959] dvb-usb: TeVii S480.1 USB successfully initialized and connected. [ 14.390661] dvb-usb: TeVii S480.1 USB successfully deinitialized and disconnected. [ 14.390917] dvb-usb: found a 'TeVii S480.2 USB' in cold state, will try to load a firmware [ 14.390972] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw' [ 14.390974] dw2102: start downloading DW210X firmware [ 14.668150] dvb-usb: found a 'TeVii S480.2 USB' in warm state. [ 14.668307] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 14.668336] DVB: registering new adapter (TeVii S480.2 USB) [ 14.668514] dvb-usb: MAC address: 68:68:68:68:68:68 [ 14.669129] Invalid probe, probably not a DS3000 [ 14.669146] dvb-usb: no frontend was attached by 'TeVii S480.2 USB' [ 14.669281] input: IR-receiver inside an USB DVB receiver as /devices/pci:00/:00:04.0/:02:00.3/usb4/4-1/input/input7 [ 14.669386] dvb-usb: schedule remote query interval to 150 msecs. [ 14.669391] dvb-usb: TeVii S480.2 USB successfully initialized and connected. [ 14.669968] dvb-usb: TeVii S480.2 USB successfully deinitialized and disconnected. [ 14.670263] usbcore: registered new interface driver dw2102 [ 15.905301] usb 3-1: config 1 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 2 [ 15.906702] usb 3-1: New USB device found, idVendor=9022, idProduct=d660 [ 15.906708] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 15.906711] usb 3-1: Product: DVBS2BOX [ 15.906714] usb 3-1: Manufacturer: TBS-Tech [ 15.907240] dvb-usb: found a 'TeVii S660 USB' in cold state, will try to load a firmware [ 15.907299] dvb-usb: downloading firmware from file 'dvb-usb-s660.fw' [ 15.907302] dw2102: start downloading DW210X firmware [ 16.068050] dvb-usb: found a 'TeVii S660 USB' in warm state. [ 16.068154] dvb-usb: will pass the complete MPEG2 transport stream to the software
[Bug 1332223] Re: [Regression] TeVii dual DVB-S S480 (=2 x DVB-S2 S660) fails to lock on channels
Running scan -x0 /usr/share/dvb/dvb-s/Astra-28.2E | tee channels.conf gives tuning failed errors for each channel, eg: DVB-S IF freq is 1782000 WARNING: tuning failed!!! tune to: 12402:v:0:27500 DVB-S IF freq is 1802000 WARNING: tuning failed!!! tune to: 12402:v:0:27500 (tuning failed) DVB-S IF freq is 1802000 WARNING: tuning failed!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1332223 Title: [Regression] TeVii dual DVB-S S480 (=2 x DVB-S2 S660) fails to lock on channels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1332223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1299252] [NEW] [needs-packaging] PyCharm Community Edition
Public bug reported: Lightweight IDE for Python Free, open-source, Apache 2 license Intelligent Editor, Debugger, Refactorings, Inspections, VCS integration Project Navigation, Testing support, Customizable UI, Vim key bindings URL: http://www.jetbrains.com/pycharm/ License: Apache 2 license Notes: Comes in Professional Edition and Community Edition, but only the Community Edition is Free software. This has already been packaged up by GetDeb: http://www.getdeb.net/app/PyCharm See also Bug #1289196 ** 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/1299252 Title: [needs-packaging] PyCharm Community Edition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1299252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249679] [NEW] Cannot click on title bars
Public bug reported: In the 13.10 release, most of the time I do not seem to be able to click the title bars (File, Edit etc). Very occasionally, it works. I can't figure out what is making the difference. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnucash 1:2.4.13-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sat Nov 9 21:46:14 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-26 (197 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnucash UpgradeStatus: Upgraded to saucy on 2013-10-05 (35 days ago) ** Affects: gnucash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249679 Title: Cannot click on title bars To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1249679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1245013] [NEW] [Regression] Vertical/Horizontal scroll along edge of touchpad not working in 13.10 (Dell 14z)
Public bug reported: I use a Dell Inspiron 14z with 13.10. I'm pretty sure that at least vertical scrolling (by moving my finger along the right edge of the touchpad) used to work, but neither work for me now in 13.10. My hardware details should be attached. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-synaptics 1.7.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sat Oct 26 17:38:37 2013 DistUpgraded: 2013-10-05 21:00:51,454 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-26 (183 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. Inspiron 5423 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=UUID=e429a76e-75c0-44b9-90d4-a75ee21d98a2 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to saucy on 2013-10-05 (20 days ago) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0RMVR3 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/03/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0RMVR3:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5423 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sat Oct 26 18:06:28 2013 xserver.configfile: default xserver.errors: RADEON(G0): [drm] Failed to open DRM device for pci::02:00.0: No such file or directory RADEON(G0): Kernel modesetting setup failed xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9020 vendor AUO xserver.version: 2:1.14.3-3ubuntu1 ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1245013 Title: [Regression] Vertical/Horizontal scroll along edge of touchpad not working in 13.10 (Dell 14z) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1245013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 503003] Re: multiple entries in fstab with same mount-point
It sounds like this also stops BindFS from working to share a local directory on boot: https://help.ubuntu.com/community/Bindfs-SharedDirectoryLocalUsers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/503003 Title: multiple entries in fstab with same mount-point To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/503003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083038] Re: Encrypted LVM in Ubiquity unavailable when installing alongside an existing OS
** Description changed: - Ubiquity installer in 12.10 offers the ability to install Ubuntu in an encrypted LVM. However, the options are only available when replacing an existing operating system. - If I wish to install Ubuntu alongside another OS, the options become grayed out (see screenshot). If I select Something else, the manual partition tool does not provide a way to install Ubuntu in an encrypted LVM. + Ubiquity installer in 12.10 and 13.04 offers the ability to install + Ubuntu with Full Disk Encryption, with checkboxes for encryption and + LVM. However, the options are only available when replacing an existing + operating system. If I wish to install Ubuntu alongside another OS, the + options become greyed out (see screenshot). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083038 Title: Encrypted LVM in Ubiquity unavailable when installing alongside an existing OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1083038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174659] [NEW] Manual partitioning doesn't allow multiple partitions within encrypted volume
Public bug reported: I use Full-Disk Encryption. It does not seem possible to set up multiple partitions within the encrypted area through the Something else manual partitioner. It is possible to create a Physical area for encrypted partitions (I'm not 100% on the wording), but as far as I can establish, you can only put one partition into that area - the + button is greyed out once one has been added. I also have Windows 7 on the machine, so I can't use the automatic set- up. What I wanted to do was set up an encrypted area (is this an LVM partition?) that I unlock with a passphrase on boot and then, within that, have my Swap, / and Home partitions. I managed to get something working by: 1) Choose Something Else 2) Add a small ext4 /boot/ partition (I did 500mb, but I think that was too big - I missed this step the first time and it errored out in a horrible way) 3) Make the rest of the free space a Encrypted physical volume or whatever it is called at the bottom of the list - this prompts you for a passphrase. 4) This adds a new section at the top of the list of partitions with a default ext4 partition that you can make / 5) Click install and ignore the warnings about no swap space See also https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/216356 which deals with both this manual partitioning point and also the ability to do this automatically alongside another OS (which is the subject of a separate bug report (Bug #1083038)). ** Affects: ubiquity (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/1174659 Title: Manual partitioning doesn't allow multiple partitions within encrypted volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1174659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174659] Re: Manual partitioning doesn't allow multiple partitions within encrypted volume
** Description changed: I use Full-Disk Encryption. It does not seem possible to set up multiple partitions within the encrypted area through the Something else manual - partitioner. + partitioner on either 12.10 or 13.04 (or any of the earlier releases). It is possible to create a Physical area for encrypted partitions (I'm not 100% on the wording), but as far as I can establish, you can only put one partition into that area - the + button is greyed out once one has been added. I also have Windows 7 on the machine, so I can't use the automatic set- up. What I wanted to do was set up an encrypted area (is this an LVM partition?) that I unlock with a passphrase on boot and then, within that, have my Swap, / and Home partitions. I managed to get something working by: 1) Choose Something Else 2) Add a small ext4 /boot/ partition (I did 500mb, but I think that was too big - I missed this step the first time and it errored out in a horrible way) 3) Make the rest of the free space a Encrypted physical volume or whatever it is called at the bottom of the list - this prompts you for a passphrase. 4) This adds a new section at the top of the list of partitions with a default ext4 partition that you can make / 5) Click install and ignore the warnings about no swap space See also https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/216356 which deals with both this manual partitioning point and also the ability to do this automatically alongside another OS (which is the subject of a separate bug report (Bug #1083038)). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174659 Title: Manual partitioning doesn't allow multiple partitions within encrypted volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1174659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1088187] Re: Scan doesn't give a preview and only saves in jpeg format
We have recently updated (new clean install) to 13.04 Raring Ringtail and this appears to have been fixed. I now have a preview when scanning and have no problems saving PDFs. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088187 Title: Scan doesn't give a preview and only saves in jpeg format To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1088187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1088187] Re: Scan doesn't give a preview and only saves in jpeg format
Sorry, I meant to say, it would be interesting to know if updating also solves your problem, Pierre - you may be able to try from a live DVD of 13.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088187 Title: Scan doesn't give a preview and only saves in jpeg format To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1088187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083038] Re: Encrypted LVM in Ubiquity unavailable when installing alongside an existing OS
I have set out how I made this work (not well) in Answer# 216356 There is no way to divide up partitions within an encrypted partition, as far as I have established. Confirmed today in 13.04. It would be good to fix this, because at the moment the manual partitioner has a whole lot of ways that this can fail if you are trying to do this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083038 Title: Encrypted LVM in Ubiquity unavailable when installing alongside an existing OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1083038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083038] Re: Encrypted LVM in Ubiquity unavailable when installing alongside an existing OS
https://answers.launchpad.net/ubuntu/+source/ubiquity/+question/216356 ** Tags added: 13.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1083038 Title: Encrypted LVM in Ubiquity unavailable when installing alongside an existing OS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1083038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1088244] Re: No Full-Disk Encryption unlock screen on some boots
I just did a clean install of 13.04 Raring Ringtail and this still occurs (on my first boot, unfortunately!) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088244 Title: No Full-Disk Encryption unlock screen on some boots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1088244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1173393] [NEW] Both my IGD Intel 4000HD and discrete ATi Radeon are powered on by default
Public bug reported: I have a Dell Insprion 14z (Inspiron 5423) and I'm running 13.04. The machine has an Intel 4000 HD and Radeon 7550M/7570M/7650M By default, both graphics cards are powered up, even though only the integrated Intel is used: $ sudo cat /sys/kernel/debug/vgaswitcheroo/switch 0:DIS: :Pwr::02:00.0 1:IGD:+:Pwr::00:02.0 The same was the case in 12.10. By default, the machine heats up terribly and the fan blasts full-tilt, with battery life affected. Each time that I reinstall Ubuntu, I have to manually edit /etc/rc.local to add the following above the exit 0: echo IGD /sys/kernel/debug/vgaswitcheroo/switch echo OFF /sys/kernel/debug/vgaswitcheroo/switch As far as I can tell, this makes no difference to performance, as by default the ATi/AMD card isn't doing anything anyway. I appreciate that, long term, the problem will hopefully be solved by powering up the discrete card as-needed and switching to that, but until we reach hybrid graphics Nirvana, perhaps the sensible option is to just turn off the discrete cards by default. I assume that it takes some jiggery-pokery to make the discrete card do anything, so adding another step to that seems less important than making sure that machines in the default setup don't overheat and have poor battery life. With the new Intel chips/drivers, they are actually a pretty good option anyway - I'm driving a 1900x1200 external monitor off mine, along with the 720p laptop monitor. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Apr 26 22:34:26 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:057f] Advanced Micro Devices [AMD] nee ATI Thames [Radeon 7550M/7570M/7650M] [1002:6841] (rev ff) (prog-if ff) InstallationDate: Installed on 2013-04-26 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. Inspiron 5423 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-19-generic root=UUID=e429a76e-75c0-44b9-90d4-a75ee21d98a2 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0RMVR3 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/03/2012:svnDellInc.:pnInspiron5423:pvrNotSpecified:rvnDellInc.:rn0RMVR3:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5423 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 raring ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173393 Title: Both my IGD Intel 4000HD and discrete ATi Radeon are powered on by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1173393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1128151] [NEW] [needs-packaging] KeePassX 2.0 Alpha 3
Public bug reported: The Alpha release of KeePassX 2.0 is available. With the poor ratings of KeePass2 on Ubuntu and KeePassX providing support for .kdbx files, it would be great to have this in Raring. I for one really would like .kdbx support, particularly now that this has been added to KeyPassDroid, as my passwords are constantly getting out of sync with my desktop and I don't know which database to keep! See https://www.keepassx.org/news/2012/10/367 General Public License ** Affects: keepassx (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/1128151 Title: [needs-packaging] KeePassX 2.0 Alpha 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepassx/+bug/1128151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 910964] Re: Cannot import photos from PTP Camera (Fuji X10)
Card with 282 photos, 7 videos. 1) Plug in camera, open Shotwell. 2) Error that camera in use by another application (pretty sure that didn't used to happen in previous versions), unmount the camera. 3) Click on the camera, all thumbnails are shown. 4) Click Import All, hangs for a while, get the attached error. ** Attachment added: Unable to lock camera: Unspecified error (-1) https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/910964/+attachment/3489728/+files/Screenshot%20from%202013-01-19%2022%3A15%3A33.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/910964 Title: Cannot import photos from PTP Camera (Fuji X10) To manage notifications about this bug go to: https://bugs.launchpad.net/libgphoto/+bug/910964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
