[Bug 1056101] Re: grub-efi overwrites an existing grub*.efi file
@mkukri A couple of years ago I had 2 installations of EndeavourOS on two different partition, and the Efi menu showed 2 different entries. I can't remember exactly but the menu entries looked like these: - EndeavourOS 12345... - EndeavourOS 14789... I don't know if the boot process is meant to work as it works in Ubuntu or as it works in EndeavourOS. At least it looks it is possible to have two different Efi menu entries for 2 different installation of the same system... and it's good. If for any reason my default system is broken and I can't access the other grub menu entries, I can still select a working system from the Efi menu. I recently had a situation like that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1056101 Title: grub-efi overwrites an existing grub*.efi file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1056101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964541] Re: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions
It looks like any kind of drag and drop doesn't work in the snap version of Firefox under Wayland session. First I've noticed that I couldn't personalize the toolbar, therefore I've open this bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1760449 Then I realized also tabs couldn't be moved. ** Bug watch added: Mozilla Bugzilla #1760449 https://bugzilla.mozilla.org/show_bug.cgi?id=1760449 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965689] Re: Black screen instead grub menu at boot
@Heinrich Schuchardt (xypron) Thanks, tried both workarounds but with no success. Didn't mention before but switching on my computer I can still get the EFI boot menu pressing F12. From there I can select any other system and set one of them as the default system at boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965689 Title: Black screen instead grub menu at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1965689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965689] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1965689/+attachment/5571166/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965689 Title: Black screen instead grub menu at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1965689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965689] Re: Black screen instead grub menu at boot
apport information ** Tags added: apport-collected wayland-session ** Description changed: Fresh install of Ubuntu 22.04 on multi-boot system. Steps: 1. Switch on computer. 2. You see for about 10 seconds a black screen instead GRUB MENU. 3. After 10 seconds Ubuntu boots normally. Extra tests: - During the 10 seconds of black screen, I can press ENTER and Ubuntu will boot. - I thought that maybe grub menu was just not visible but still there, so I've tried to use "arrow keys" (up and down) to select a different system and then press Enter... but nothing happened, the screen remained black. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu79 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-03-19 (1 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220318) + Package: grub2 (not installed) + ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 + Tags: wayland-session jammy + Uname: Linux 5.15.0-23-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1965689/+attachment/5571165/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965689 Title: Black screen instead grub menu at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1965689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965689] [NEW] Black screen instead grub menu at boot
Public bug reported: Fresh install of Ubuntu 22.04 on multi-boot system. Steps: 1. Switch on computer. 2. You see for about 10 seconds a black screen instead GRUB MENU. 3. After 10 seconds Ubuntu boots normally. Extra tests: - During the 10 seconds of black screen, I can press ENTER and Ubuntu will boot. - I thought that maybe grub menu was just not visible but still there, so I've tried to use "arrow keys" (up and down) to select a different system and then press Enter... but nothing happened, the screen remained black. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965689 Title: Black screen instead grub menu at boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1965689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944477] Re: Wayland - double monitor: edge tiled windows change position after suspension
** Tags added: hirsute impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944477 Title: Wayland - double monitor: edge tiled windows change position after suspension To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1944477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1944477] [NEW] Wayland - double monitor: edge tiled windows change position after suspension
Public bug reported: - System: Ubuntu 21.04 (experienced also with Ubuntu 21.10) - Wayland session - Hardware setup: laptop connected to 2 extra monitors - Laptop screen: off - Samsung (left monitor): on - LG (right monitor): on - DESCRIPTION Edge tiled windows can be placed in a different position after suspension. See this video example https://www.youtube.com/watch?v=xL1VlzDh2CU In the video you can see that Gedit is placed on the left side of the monitor on the right. After suspension Gedit is moved to the left side of the left screen. It looks that this bug happens only with windows tiled at the edges between two monitors. Unfortunately it seems to be random, it happens often but not every time. - REPRODUCE THE BUG 1. Left monitor: place a window using the tiling window functionality on the right side. 2. Right monitor: place a window using the tiling window functionality on the left side. 3. Suspend the computer. 4. Switch on the computer. Now it's possible the one or both windows are in a different position. - NOTES This problem is related to Wayland session but I don't know exactly which components (maybe Mutter?). Please let me know if some specific commands is needed. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: hirsute impish wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1944477 Title: Wayland - double monitor: edge tiled windows change position after suspension To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1944477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925187] Re: error: Running 'grub-install --force --target x86_64-efi "/dev/sda"' failed.
@seb128 Yes correct, it was automatic partitioning. I've chosen the "Install Ubuntu alongside.." option: https://postimg.cc/N2hnmtxR -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925187 Title: error: Running 'grub-install --force --target x86_64-efi "/dev/sda"' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1925187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924823] Re: ESP on install medium automatically configured as ESP for install, failing install
Just to confirm everything I've written in message #25. I've repeated the same tests with the deily iso 20/4. The workaround at message #13 is no more needed for Ubuntu 21.04, but it can still be useful for Ubutnu 20.10 The step: sudo apt install --reinstall grub-pc can be more easily replaced by: sudo update-grub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924823 Title: ESP on install medium automatically configured as ESP for install, failing install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924856] Re: Ubiquity creates useless ESR (EFI) partition on Bios system
> juliank > This is a feature, not a bug. It's what I thought once I was aware of all these troubles: https://discourse.ubuntu.com/t/groovy-to-use-grub2-for-booting-installer-media-in-any-modes-on-all-architectures/16871/34 But it looks like nobody knew about EFI partition with BIOS and I've been asked to file a bug report about it. Fortunately year after year we are going to have less old computers based on old BIOS and also Ubuntu 20.10 and 21.04 are not LTS version and therefore not so popular. But a feature like this should have been "loudly" communicated to all users before landing into the installer, after decades with no need of EFI partition with BIOS. And should have been also bullet proof tested before landing to users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924856 Title: Ubiquity creates useless ESR (EFI) partition on Bios system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924823] Re: ESP on install medium automatically configured as ESP for install, failing install
Hi everybody, As guiverc I have updated Ubiquity on a older Ubuntu iso image to get version 21.04.19 In good part I can confirm good news! ...but there are still bizarre things I've performed 2 test installation: 1- MANUALLY CHOSING A PARTITION Same result reported by guiverc at comment #24 The bad thing is the message 'No EFI Partition found. This system will likely not be able to boot... please go back and add an EFI...' This can be tricky! 2- INSTALL ALONGSIDE... (in remaining disk space - 3 partition already taken on MBR) That's a typical situation seen many times on old computers with Windows7 that already takes 3 partitions. It finally works! But it's quite weird. During the installation the well known grub error message "Executing 'grub-install /dev/sda' failed This is a fatal error" appears. But rebooting the system everything is fine. I'm actually writhing from the installed system. I'm afraid that the error message can be even trickier than the message in the previous case. I've filed bug #1925187 before rebooting the system not knowing if the system could boot. Then I've changed title and description... anyway, log files are there for further information. I presume there is no much time before the release dayleft for a 'cleaner' solution. It's a pity that only now someone is doing something against these issues. Anyway... juliank and also jibel, thank you very much for all the efforts. P.S. I'll probably repeat the tests when the new daily-build is out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924823 Title: ESP on install medium automatically configured as ESP for install, failing install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925187] Re: Ubiquity 21.04.19 ends in 'error install grub' but Ubuntu get installed
** Description changed: Ubiquity 21.04.19 installed via apt on a previous iso daily-build as an iso with 21.04.19 at the moment is not available. DESCRIPTION: - Partition table: msdos (MBR) - /dev/sda1 with Ubuntu already installed - /dev/sda2 and /dev/sda3 both Ext4 Installation modality: Install Ubuntu 21.04 alongside... As 3 primary partition are already used, the installer is forced to use the remaining space creating an extended partition with logical partition inside: - /dev/sda5 ESP (EFI) - /dev/sda6 Ext4 for Ubuntu - But EFI partition should be primary, not logical. + EFI partition should be primary, not logical and as expected a popup: + Executing 'grub-install /dev/sda' failed + This is a fatal error - Then grub-install fails. + Despite this the system get installed and it is bootable. + Probably because of the recent changes on Ubiquity package. + + Anyway, the 'grub error' message can be tricky! + ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.19 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Tue Apr 20 06:42:08 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210416) RebootRequiredPkgs: - linux-image-5.11.0-16-generic - linux-base - linux-image-5.11.0-14-generic - linux-base + linux-image-5.11.0-16-generic + linux-base + linux-image-5.11.0-14-generic + linux-base SourcePackage: ubiquity 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/1925187 Title: Ubiquity 21.04.19 ends in 'error install grub' but Ubuntu get installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1925187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925187] Re: Ubiquity 21.04.19 ends in 'error install grub' but Ubuntu get installed
** Summary changed: - Ubiquity 21.04.19 fails in 'install alongside' in extended partition + Ubiquity 21.04.19 ends in 'error install grub' but Ubuntu get installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925187 Title: Ubiquity 21.04.19 ends in 'error install grub' but Ubuntu get installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1925187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925187] [NEW] Ubiquity 21.04.19 fails in 'install alongside' in extended partition
Public bug reported: Ubiquity 21.04.19 installed via apt on a previous iso daily-build as an iso with 21.04.19 at the moment is not available. DESCRIPTION: - Partition table: msdos (MBR) - /dev/sda1 with Ubuntu already installed - /dev/sda2 and /dev/sda3 both Ext4 Installation modality: Install Ubuntu 21.04 alongside... As 3 primary partition are already used, the installer is forced to use the remaining space creating an extended partition with logical partition inside: - /dev/sda5 ESP (EFI) - /dev/sda6 Ext4 for Ubuntu But EFI partition should be primary, not logical. Then grub-install fails. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.19 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Tue Apr 20 06:42:08 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210416) RebootRequiredPkgs: linux-image-5.11.0-16-generic linux-base linux-image-5.11.0-14-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubiquity-21.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925187 Title: Ubiquity 21.04.19 fails in 'install alongside' in extended partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1925187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924823] Re: ESP on install medium automatically configured as ESP for install, failing install
> juliank > Jeremie, the correct workaround is to deselect the EFI system partition when > you configure partitions in the installer, as I explained in comment #5. Let's say that the EFI partition is not selected, it only shows the type (EFI) but it's not selected a mount point. As reported in comment #10 I have also tried the installation explicitly selecting "don't use this partition" for the EFI on the USB stick. But it didn't work, same problems of the other attempts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924823 Title: ESP on install medium automatically configured as ESP for install, failing install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems
> juliank: > Jeremie, you reported a separate bug for the issue of the installer > automatically picking > up the USB stick's USB, please comment there if you have to. I know and I apologize, but here is where many other users experienced problems related to EFI/BIOS and I thought it could be a good thing to let them know of this alternative workaround, surely less intimidating than chroot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893964 Title: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems
@lproven Good observation. The EFI boot partition is created inside USB device at least with the latest versions of major gui utilities available in Ubuntu: gnome-disk-utility and usb-creator-gtk. balenaEtcher also does it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893964 Title: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems
There's an easier WORKAROUND in case you have no space for an extra EFI partition. First of all a resume of the issues related to 'EFI on BIOS'. The system itself get installed. Problem is that Ubiquity thinks that an ESR (EFI) partition is needed even on computers with BIOS. And it does installs grub, but on the USB install device. This because it finds an EFI partition in the USB device and automatically selects it bug #1924823 It's still possible to boot the installed system just keeping the USB device connected to computer. The WORKAROUND works like this: boot the system, modified /etc/fstab, remove grub-efi* package and re-installed grub-pc. HERE ALL THE STEPS: 1. Make sure 'first boot from hard disk' is set in the BIOS settings. 2. Connect the USB installer device and start the computer. 3. Open /etc/fstab and comment the line related to /boot/efi: sudo -H gedit /etc/fstab 4. find a line like this: UUID=BF7E1-08E7 /boot/efi vfat umask=0077 0 1 5. put the character # at the beginning of the line: #UUID=BF7E1-08E7 /boot/efi vfat umask=0077 0 1 6. Save the file and exit from gedit. 7. Un-mount e mount the partitions: sudo umount -a && sudo mount -a 8. Uninstall all grub-efi related packages: sudo apt purge grub-efi* 9. Reinstall grub-pc: sudo apt install --reinstall grub-pc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893964 Title: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924823] Re: ESP on install medium automatically configured as ESP for install, failing install
Got the WORKAROUND and it's quite easy :D (Thanks guiverc, you gave the idea!) As you have done I tried to boot the system keeping the USB installer device connected to the computer. I've just set 'first boot from hard disk' inside bios settings... and the system boots. Then I've uninstalled grub-efi* package, modified /etc/fstab and re-installed grub-pc. It worked! HERE ALL THE STEPS: 1. Make sure 'first boot from hard disk' is set in the BIOS settings. 2. Connect the USB installer device and start the computer. 3. Open /etc/fstab and comment the line related to /boot/efi: sudo -H gedit /etc/fstab 4. find a line like this: UUID=BF7E1-08E7 /boot/efi vfat umask=0077 0 1 5. put the character # at the beginning of the line: #UUID=BF7E1-08E7 /boot/efi vfat umask=0077 0 1 6. Save the file and exit from gedit. 7. Un-mount e mount the partitions: sudo umount -a && sudo mount -a 8. Uninstall all grub-efi related packages: sudo apt purge grub-efi* 9. Reinstall grub-pc: sudo apt install --reinstall grub-pc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924823 Title: ESP on install medium automatically configured as ESP for install, failing install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924856] Re: Ubiquity creates useless ESR (EFI) partition on Bios system
** Description changed: Ubuntu 21.04 - 16/4 daily build - Ubiquity 21.04.15 Even on computers with old BIOS an ESR (EFI) partition will be automatically created when installing Ubuntu using one of the automatic options like "Erase disk and install Ubuntu", "Install Ubuntu alongside other system", etc.. This should not happens. No ESR partition should be created on systems with old BIOS. In this case: - 2 partition where already existing: - /dev/sda1 Ext4 with Ubuntu 21.04 already installed - /dev/sda2 Ext4 empty - Performed the "Install Ubuntu alongside other system" install option". - After install: - - /dev/sda3 Fat32 ESP - - /dev/sd4 extended - - /dev/sda5 Ext4 with new Ubuntu 21.04 + - /dev/sda3 Fat32 ESP + - /dev/sd4 extended + - /dev/sda5 Ext4 with new Ubuntu 21.04 I've set just 2 existing primary partition because if the installer doesn't find a primary partition for ESR, installation will fail and that's another bug, see bug #1924823 In this case installation will succeed, but just think about all the - system on old BIOS that are already using 3 primary partitions and + systems with old BIOS that are already using 3 primary partitions and there's no extra primary partition for ESR.. in that case installation fails. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 17 16:04:41 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.11.0-14-generic linux-base SourcePackage: ubiquity 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/1924856 Title: Ubiquity creates useless ESR (EFI) partition on Bios system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924856] Re: Ubiquity creates useless ESR (EFI) partition on Bios system
** Description changed: Ubuntu 21.04 - 16/4 daily build - Ubiquity 21.04.15 Even on computers with old BIOS an ESR (EFI) partition will be automatically created when installing Ubuntu using one of the automatic options like "Erase disk and install Ubuntu", "Install Ubuntu alongside other system", etc.. - This should not happens. No ESR partition should be created. + This should not happens. No ESR partition should be created on systems + with old BIOS. In this case: - 2 partition where already existing: - /dev/sda1 Ext4 with Ubuntu 21.04 already installed - /dev/sda2 Ext4 empty - - Performed the "Install Ubuntu alongside other system" install option. + - Performed the "Install Ubuntu alongside other system" install option". + - After install: + - /dev/sda3 Fat32 ESP + - /dev/sd4 extended + - /dev/sda5 Ext4 with new Ubuntu 21.04 I've set just 2 existing primary partition because if the installer doesn't find a primary partition for ESR, installation will fail and that's another bug, see bug #1924823 In this case installation will succeed, but just think about all the system on old BIOS that are already using 3 primary partitions and there's no extra primary partition for ESR.. in that case installation fails. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 17 16:04:41 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.11.0-14-generic linux-base SourcePackage: ubiquity 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/1924856 Title: Ubiquity creates useless ESR (EFI) partition on Bios system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924823] Re: ESP on install medium automatically configured as ESP for install, failing install
Some more info: - I repeated the installation selecting the "don't use this partition" option for the EFI partition of the USB device. The result is still the same like in the example of guiverc: /dev/sda1 on /target type ext4 /dev/sdb2 on /target/boot/efi - I filed a new bug report: bug #1924856 I thought it might be useful to have some data when installation succeed using one of the automatic option. In this case I've selected "Install Ubuntu alongside other system". An ESR partition is automatically created on /dev/sda3. Till Ubuntu 20.04 everything was fine. There still were two different modality to boot the USB/dvd device: "uefi modality" and "old bios modality". All these issues started with Ubuntu 20.10 where the way to boot the USB/dvd device is now unified. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924823 Title: ESP on install medium automatically configured as ESP for install, failing install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924856] Re: Ubiquity creates useless ESR (EFI) partition on Bios system
** Description changed: Ubuntu 21.04 - 16/4 daily build - Ubiquity 21.04.15 Even on computers with old BIOS an ESR (EFI) partition will be automatically created when installing Ubuntu using one of the automatic options like "Erase disk and install Ubuntu", "Install Ubuntu alongside other system", etc.. This should not happens. No ESR partition should be created. In this case: - 2 partition where already existing: - - /dev/sda1 Ext4 with Ubuntu 21.04 already installed - - /dev/sda2 Ext4 empty + - /dev/sda1 Ext4 with Ubuntu 21.04 already installed + - /dev/sda2 Ext4 empty + - Performed the "Install Ubuntu alongside other system" install option. I've set just 2 existing primary partition because if the installer doesn't find a primary partition for ESR, installation will fail and that's another bug, see bug #1924823 In this case installation will succeed, but just think about all the system on old BIOS that are already using 3 primary partitions and there's no extra primary partition for ESR.. in that case installation fails. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 17 16:04:41 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210416) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=it_IT.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=it_IT.UTF-8 + SHELL=/bin/bash RebootRequiredPkgs: - linux-image-5.11.0-14-generic - linux-base + linux-image-5.11.0-14-generic + linux-base SourcePackage: ubiquity 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/1924856 Title: Ubiquity creates useless ESR (EFI) partition on Bios system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924856] [NEW] Ubiquity creates useless ESR (EFI) partition on Bios system
Public bug reported: Ubuntu 21.04 - 16/4 daily build - Ubiquity 21.04.15 Even on computers with old BIOS an ESR (EFI) partition will be automatically created when installing Ubuntu using one of the automatic options like "Erase disk and install Ubuntu", "Install Ubuntu alongside other system", etc.. This should not happens. No ESR partition should be created. In this case: - 2 partition where already existing: - /dev/sda1 Ext4 with Ubuntu 21.04 already installed - /dev/sda2 Ext4 empty I've set just 2 existing primary partition because if the installer doesn't find a primary partition for ESR, installation will fail and that's another bug, see bug #1924823 In this case installation will succeed, but just think about all the system on old BIOS that are already using 3 primary partitions and there's no extra primary partition for ESR.. in that case installation fails. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 17 16:04:41 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.11.0-14-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubiquity-21.04.15 ubuntu ** Summary changed: - Ubiquity create useless ESR (EFI) partition on Bios system + Ubiquity creates useless ESR (EFI) partition on Bios system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924856 Title: Ubiquity creates useless ESR (EFI) partition on Bios system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924823] Re: ESP on install medium automatically configured as ESP for install, failing install
Hi and thanks for your reply. I'm going to do some more tests. Anyway, if you select "Erase the disk and install Ubuntu" the installer is going to create an ESP on /dev/sda (see the attached picture). I didn't perform this type of installation (I did it few months ago and it actually create the ESP partition) I just wanted to see if the installer was still doing this. It looks like it doesn't matter what your are doing, the installer is "acting" like the only existing system is UEFI. ** Attachment added: "Picture of ESP + / before installling Ubuntu" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+attachment/5489212/+files/automatic_esp.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924823 Title: ESP on install medium automatically configured as ESP for install, failing install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems
Hi, I've tried to install the 16/4 daily build with Ubiquity 21.04.15, but I'm still experiencing the same problems. I've just in case filed this bug report: bug #1924823 I've tried to manually install Ubuntu on one of the Ext4 primary partition. Didn't try any other modality, just seen that selecting the "install on the entire disk" option a popup window tells that an ESR partition will be created. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893964 Title: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924823] [NEW] Ubiquity Ubuntu 21.04 install fail on legacy bios
Public bug reported: This bug report is a duplicated of bug #1902269 performed with Ubuntu 21.10. Basically installation fail when the installer doesn't find an EFI (ESR) partition on computers with legacy BIOS. This time I have used Ubuntu 21.04 also to test the new version of Ubiquity package (21.04.15) which, as reported here: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/comments/22 should have fixed the issue. Unfortunately I'm still experiencing the same problem. Partition details: - msdos partition table - 4 primary partitions, all ext4 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Sat Apr 17 02:20:20 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210416) RebootRequiredPkgs: linux-image-5.11.0-14-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubiquity-21.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924823 Title: Ubiquity Ubuntu 21.04 install fail on legacy bios To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1924823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems
Same problem on 21.04, Ubuntu installer thinks that BIOS is UEFI. Just 2 months left before the the final release. Any chance for a fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893964 Title: Installation of Ubuntu Groovy with manual partitioning without an EFI System Partition fails on 'grub-install /dev/sda' even on non-UEFI systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864871] Re: Failed to init Intel sound card in 20.04
After many months, I had the opportunity to put my hands on the computer that had these audio problems: (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/comments/31) ...and now the audio works without any workaround. Current Ubuntu version: 20.04.2 Kernel: 5.8.0-41 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864871 Title: Failed to init Intel sound card in 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
@Timo Aaltonen The new package fix the problem. Good job! Here what I've done: 1. enabled the proposed repository 2. updated gnome-shell-extension-desktop-icons to version 20.04.0+git20200908-5~ubuntu20.10.0 3. Test case: created a file in the desktop and tried drag & drop inside an open folder. As expected drag & drop doesn't work, but now the shell doesn't freeze. ** Tags removed: verification-needed-groovy ** Tags added: verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901137] Re: UEFI on Legacy - grub-install fails due to no space left on ESP
My bug report #1902269 has been marked as duplicated of this one even if the description it's not exactly the same. In any case it looks the problem is related to the EFI (ESP) partition, that should never be used on old BIOS or UEFI in Legacy Mode, but for some reasons the installer want it... even if we are NOT in "UEFI mode". This might be related to recent changes of the installer https://discourse.ubuntu.com/t/groovy-to-use-grub2-for-booting-installer-media-in-any-modes-on-all-architectures/16871 You have probably noticed that now there's no difference between uefi or bios mode. When you boot the live USB, you see the same grub menu. After many tests, these are the case where the installation has been successful: - updating the system directly from Focal (from 20.04 to 20.10) - creating an EFI partition during manual partitioning. In this case the partition must be a primary partition. (One user was able to set the EFI partition on a USB drive... it was not my case). - Installing Ubuntu using the "Erase the disk and install Ubuntu.." will also succeed. EFI partition will be automatically created. (Also the option "Install Ubuntu next Windows" should work, but there must be enough space for a primary partition for the EFI). As reported on bug #1893964 (comment #8), the user was able to install the system skipping the "grub-install" launching Ubiquity with the command: ubiquity -b Then he manually recovered GRUB. I've tried the same, but with no success... still had problems with efi. The log reported several errors and one of them was: ## pc systemd[1]: Dependency failed for /boot/efi. ## Subject: L'unità boot-efi.mount è fallita ## Defined-By: systemd ## Support: http://www.ubuntu.com/support I hope there will be a solution as soon as possible, this is one of the worst bug ever :( The only lucky thing is that Ubuntu 20.10 is NOT a LTS... other wise many more users could have been in trouble. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901137 Title: UEFI on Legacy - grub-install fails due to no space left on ESP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1901137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902269] Re: Ubuntu 20.10 on BIOS hardware - Installation with manual partitioning fails while executing "grub-install /dev/sda"
** Description changed: (I'm duplicating this bug https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964 in order to provide more data to developers). Installation with manual partitioning of Ubuntu 20.10 on BIOS hardware fails while executing "grub-install /dev/sda". We already know as reported in bug #1893964 that this happens because for some reasons the installation system expect an existing EFI boot partition. On the same machine I have also tried to install Ubuntu 20.10 using the automatic option "Erase the disk and install Ubuntu..". In that case the installation succeeds, with the automatic creation of the EFI partition. Of course being an old computer with old BIOS, there should not be any need of an EFI partition on a msdos(mbr) partition table. - Here what I've done: ::: BEFORE INSTALLATION With Gparted I have: 1- erased the hard disk 2- created an msdos partion table 3- created a 50GiB Ext4 partition ::: INSTALLATION I've run a standard installation: - enabled 3rd party software - chosen the manual partitioning - selected the only partition available, formatted as Ext4 and set "/" as mount point ::: CRASH At one point installation stops with popup window showing: "Executing 'grub-install /dev/sda' failed. This is a fatal error." + ::: WORKAROUND + + Just create an EFI partition before installing the system. + + ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 30 16:33:29 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash RebootRequiredPkgs: - linux-image-5.8.0-25-generic - linux-base + linux-image-5.8.0-25-generic + linux-base SourcePackage: ubiquity 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/1902269 Title: Ubuntu 20.10 on BIOS hardware - Installation with manual partitioning fails while executing "grub-install /dev/sda" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1902269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902269] [NEW] Ubuntu 20.10 on BIOS hardware - Installation with manual partitioning fails while executing "grub-install /dev/sda"
Public bug reported: (I'm duplicating this bug https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964 in order to provide more data to developers). Installation with manual partitioning of Ubuntu 20.10 on BIOS hardware fails while executing "grub-install /dev/sda". We already know as reported in bug #1893964 that this happens because for some reasons the installation system expect an existing EFI boot partition. On the same machine I have also tried to install Ubuntu 20.10 using the automatic option "Erase the disk and install Ubuntu..". In that case the installation succeeds, with the automatic creation of the EFI partition. Of course being an old computer with old BIOS, there should not be any need of an EFI partition on a msdos(mbr) partition table. Here what I've done: ::: BEFORE INSTALLATION With Gparted I have: 1- erased the hard disk 2- created an msdos partion table 3- created a 50GiB Ext4 partition ::: INSTALLATION I've run a standard installation: - enabled 3rd party software - chosen the manual partitioning - selected the only partition available, formatted as Ext4 and set "/" as mount point ::: CRASH At one point installation stops with popup window showing: "Executing 'grub-install /dev/sda' failed. This is a fatal error." ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.13 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 30 16:33:29 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: linux-image-5.8.0-25-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.13 ubuntu ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1902269/+attachment/5429521/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902269 Title: Ubuntu 20.10 on BIOS hardware - Installation with manual partitioning fails while executing "grub-install /dev/sda" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1902269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864871] Re: Failed to init Intel sound card in 20.04
Similar problem with: - Ubuntu 20.04 LTS - Fujitsu LifeBook A530 - $ lspci | grep Audio 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) THE PROBLEM: No sound. Gnome audio system settings shows "Dummy Audio" as output device. Trying with Lubuntu 20.04 on a different partition there's the same problem but running PulseAudio Volume Control it's possible to select: "analog stereo duplex" or "analog stereo output". Unfortunately there is no setting like this for Gnome. WORKAROUND: As reported here https://forum.ubuntu-it.org/viewtopic.php?t=413914 it seems to be a problem related to udev which doesn't find the audio card. 1. Inside /etc/pulse/default.pa find the following code: .ifexists module-udev-detect.so load-module module-udev-detect .else ### Alternatively use the static hardware detection module (for systems that ### lack udev support) load-module module-detect .endif 2. Comment the if/else statement: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Alternatively use the static hardware detection module (for systems that ### lack udev support) load-module module-detect #.endif 3. Save the file and restart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864871 Title: Failed to init Intel sound card in 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1864871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865169] Re: volume and light not working in Gnome Shell 3.35
Just to confirm gjs version 1.63.92-1 fixes the problem. (P.S. focal-proposed activated) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865169 Title: volume and light not working in Gnome Shell 3.35 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1056101] Re: grub-efi overwrites an existing grub*.efi file
Bug is still there. Quick example when my computer starts: if I don't do anything, Ubuntu 19.10 will be booted. If I press [F12] I get the Boot Menu list, which shows: 1. ubuntu 2. deepin 3. CD/DVD Drive ... 4. Drive0 HDD ... There is only 1 entry for Ubuntu (which is the one for 19.10) but on my computer there are totally 4 different Ubuntu releases: - Ubuntu 14.04 - Ubuntu 19.04 - Ubuntu 19.10 - Ubuntu 20.04 They should be all mentioned in the Boot Menu, but there is just one entry. If you install one of the Ubuntu versions, it will be automatically set as the only "ubuntu" Boot Menu entry. It will also be set as the default system on boot. To change it you have to boot the Ubuntu version you want as the default one at boot, and run the command "sudo grub-install". P.S. I apologize for my old messages (#2 and #3) as they were not strictly connected to this bug, sorry! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1056101 Title: grub-efi overwrites an existing grub*.efi file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1056101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820432] [NEW] Top bar Application Menu cannot be hidden
Public bug reported: Gnome Tweaks in Ubuntu 19.04 Selecting "Top Bar -> Application Menu", there is no way to hide the app menu. I suppose this happens because the app menu has been changed in the latest Gnome Shell version and that's why the switch has no effect. ** Affects: gnome-tweaks (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/1820432 Title: Top bar Application Menu cannot be hidden To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1820432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733394] Re: Mines does not recognize a new high score has happened
Mines 3.26.0 - Ubuntu 17.10 I found a related upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=789399 ** Bug watch added: GNOME Bug Tracker #789399 https://bugzilla.gnome.org/show_bug.cgi?id=789399 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733394 Title: Mines does not recognize a new high score has happened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-mines/+bug/1733394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Hi, Another main problem is that the *buntu 17.10 ISO images are still down-loadable. Not all the users read linux news and are aware of this bad bug. Unfortunately a warning on the ubuntu.com download page is not enough. There are infinite ways to reach the download links of the 17.10. Also, does anyone know if the ISO images are going to be updated with an updated kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631750] Re: Language installation doesn't work in Ubuntu GNOME 16.10 Settings app
I found the same problem with the language setup on Ubuntu 17.10. This could be related to the new Gnome Settings (just let me know if you think I should open a new bug report). I was running Ubuntu 17.10 in Italian language, previously installed with the old Gnome Settings. I wanted to switch to English language but I couldn't because of this bug. Following the steps of the bug description, the only difference was the terminal warning: "Language it_IT not installed, trying to install it" ..which is a bit strange because the system was already set to Italian, I wanted to set the en_US.UTF-8. I've noticed that while trying to change the language settings, the strings in /etc/default/locale don't change at all. :: WORKAROUND 1- sudo nano /etc/default/locale 2- Comment or delete the existing strings end write the following: LANG="en_US.UTF-8" LANGUAGE="en" If I want to go back to the Italian setup I just need to write the following: LANG="it_IT.UTF-8" LANGUAGE="it:en" 3- Press [Ctrl]+O and [Enter] to save the file. Press then [Ctrl]+X to exit from Nano editor. 4- Log-out and log-in again or restart the system. After the log-in the system is asking if you would like to update the names of the folders into $HOME (Desktop, Music, Video, etc..). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631750 Title: Language installation doesn't work in Ubuntu GNOME 16.10 Settings app To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1631750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716341] Re: Settings for external monitor are deleted after reboot, suspension, log out
** Summary changed: - Settings for external monitor are delete after reboot, suspension, log out + Settings for external monitor are deleted after reboot, suspension, log out -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716341 Title: Settings for external monitor are deleted after reboot, suspension, log out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1716341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714410] Re: Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig
I have open a new bug related to the fact that gnome settings doesn't "remember" the setup for external monitors after log out, restart.. Please add comment here: https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/1716341 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714410 Title: Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1714410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716341] [NEW] Settings for external monitor are delete after reboot, suspension, log out
Public bug reported: New Gnome Settings on Ubuntu 17.10 Settings for external monitor are working but after reboot/suspension /log-out log-in, the system will not remember the setup. Example: 1- open Gnome Settings and select "Devices → Displays" 2- set the external monitor as "Single Display" and click on "Apply" 3- log-out After log-in the laptop monitor will be set as default instead of the external monitor. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: artful ** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716341 Title: Settings for external monitor are delete after reboot, suspension, log out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1716341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714410] Re: Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig
After the latest updates with the new Gnome Settings I can change the setup for external monitors. The problem is that the system doesn't remember the settings, so after a log out (or restart or suspension, etc..) I need always to open again Gnome Settings and set the external monitor as "Single Display". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714410 Title: Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1714410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715021] Re: Gnome settings for primary/secondary monitor are not working
*** This bug is a duplicate of bug 1714410 *** https://bugs.launchpad.net/bugs/1714410 @Peter Magnusson Thanks, I've marked the report as duplicated of Bug #1714410. Hopefully this bug will disappear once the new Gnome Settings will be updated to the new version https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/1714410/comments/4 ** This bug has been marked a duplicate of bug 1714410 Can't change display configuration, Method ApplyConfiguration is not implemented on interface org.gnome.Mutter.DisplayConfig -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715021 Title: Gnome settings for primary/secondary monitor are not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1715021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715021] [NEW] Gnome settings for primary/secondary monitor are not working
Public bug reported: Fresh install of Ubuntu 17.10 (laptop + external monitor). Running "Settings → Displays → Primary (or Secondary)", all the options: - Primary - Secondary Display - Mirror - Turn Off are not working. Also "Arrange Combined Displays" is not working. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.24.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 4 22:33:37 2017 InstallationDate: Installed on 2017-09-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: artful gnome-17.10 ** Tags removed: amd64 apport-bug ** Tags added: gnome-17.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715021 Title: Gnome settings for primary/secondary monitor are not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1715021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1710145] [NEW] "mid-click lower" not woking with headerbar in Wayland session
Public bug reported: Ubuntu 17.10 - WAYLAND SESSION Mid-click lower (it can be set with Tweaks → Windows → Titlebar Actions → Middle Click → Lower) doesn't work any more with all the Gnome applications that use the new titlebar (headerbar). It's still working with some apps that use the classic titlebar (like Firefox, Gimp, Nemo..). While with other apps (LibreOffice, Transmission..) it seems to have problems too. No problem at all using the old Xorg-session. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome (not installed) ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 11 13:53:20 2017 InstallationDate: Installed on 2017-07-20 (22 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170719) SourcePackage: meta-gnome3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: meta-gnome3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful 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/1710145 Title: "mid-click lower" not woking with headerbar in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-gnome3/+bug/1710145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577120] Re: Mounted NFS share prevents shutdown
@Sean I tried your fstab entry and it works perfectly, even if I switch off the computer immediately after the boot. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577120 Title: Mounted NFS share prevents shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577120] Re: Mounted NFS share prevents shutdown
OK, it seems that workaround #4 works if I wait a bit before shutdown/reboot. If I switch off the computer immediately after the boot, the problem will still be there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577120 Title: Mounted NFS share prevents shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577120] Re: Mounted NFS share prevents shutdown
@Sean I have tried to use your workaround #4 but unfortunately didn't work on my computer. Please could you let me know which options are you using on your /etc/fstab? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577120 Title: Mounted NFS share prevents shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1577120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376212] Re: BQ Aquaris E4.5 Android Phone not recognised by libmtp
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376212 Title: BQ Aquaris E4.5 Android Phone not recognised by libmtp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1376212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1376212] Re: BQ Aquaris E4.5 Android Phone not recognised by libmtp
Hi Brian, It works. I've just enabled the -proposed and installed the libmtp 1.1.6-20-g1b9f164-1ubuntu2.1 package. Then I've connected the BQ 4.5 via USB.cable. Nautilus starts automatically as expected. Thanks, well done! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1376212 Title: BQ Aquaris E4.5 Android Phone not recognised by libmtp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1376212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467649] [NEW] bq 4.5 not mounting on Ubuntu 14.04
Public bug reported: Ubuntu 14.04 doesn't mount the BQ Aquaris 4.5 once it is connected with usb cable. Everything works fine on Ubuntu 14.10 and 15.04. Workaround (found here http://ubuntuforums.org/showthread.php?t=2270325) Installing an updated version of libmtp from this repo https://launchpad.net/~phablet-team/+archive/ubuntu/tools: sudo add-apt-repository ppa:phablet-team/tools sudo apt-get update sudo apt-get upgrade libmtp-common, libmtp-runtime and libmtp9 will be updated. Once connected via usb, the smart phone will be browsable from the file manager and the icon will appear on the launcher. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libmtp-common 1.1.6-20-g1b9f164-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 22 21:09:18 2015 Dependencies: InstallationDate: Installed on 2015-03-15 (99 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: libmtp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libmtp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467649 Title: bq 4.5 not mounting on Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1467649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283849] Re: New window decorations break middle click title bar
The middle click problem came back in Ubuntu 15.04. (Also tried the daily-live 26-Mar iso 64bit) I had a look into dconf-editor and unfortunately there's no way to set lower in /org/gnome/desktop/wm/preferences/action-middle-click- titlebar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283849 Title: New window decorations break middle click title bar To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283849] Re: New window decorations break middle click title bar
Thank you very much Lem, it works with Unity Tweak Tool. In the meantime I discovered that it works also running the following command: $ dconf write /org/gnome/desktop/wm/preferences/action-middle-click- titlebar 'lower' It might sound crazy, but this is one of the most important feature to me! Anyway, it would be nice to have the mid-click on the title bar working again by default :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283849 Title: New window decorations break middle click title bar To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416463] [NEW] MoinMoin tableclass not working
Public bug reported: (python-moinmoin 1.9.7 on Ubuntu 14.04) Tried to creat a class in the .css file for tables without borders, but testing the class in a wiki page, like this: ||tableclass=noborder ... || ... || didn't work. As a workaround I tried to remove the double quotes: ||tableclass=noborder ... || ... || It worked and I had the table without borders. Basically the double quotes create problems to the html code. This bug seems to be already known https://moinmo.in/MoinMoinBugs/1.9.7Table_styles/class%20not%20working I also tried the new moinmoin version 1.9.8 and found that both ways to write the class, with or without double quotes, are working (tableclass=noborder and tableclass=noborder). Is there any chance to get the 1.9.8 into the Ubuntu repos? Thanks! ** Affects: moin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to moin in Ubuntu. https://bugs.launchpad.net/bugs/1416463 Title: MoinMoin tableclass not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/moin/+bug/1416463/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1416463] [NEW] MoinMoin tableclass not working
Public bug reported: (python-moinmoin 1.9.7 on Ubuntu 14.04) Tried to creat a class in the .css file for tables without borders, but testing the class in a wiki page, like this: ||tableclass=noborder ... || ... || didn't work. As a workaround I tried to remove the double quotes: ||tableclass=noborder ... || ... || It worked and I had the table without borders. Basically the double quotes create problems to the html code. This bug seems to be already known https://moinmo.in/MoinMoinBugs/1.9.7Table_styles/class%20not%20working I also tried the new moinmoin version 1.9.8 and found that both ways to write the class, with or without double quotes, are working (tableclass=noborder and tableclass=noborder). Is there any chance to get the 1.9.8 into the Ubuntu repos? Thanks! ** Affects: moin (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/1416463 Title: MoinMoin tableclass not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/moin/+bug/1416463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1056101] Re: grub-efi overwrites an existing grub*.efi file
Today I was updating one of the system (Lubuntu) on one of my test partitions. The system wasn't the default one at the boot, but as the grub packages have been updated, after the re-boot I have discovered that it was set as the boot default system... This bug creates problems even with the updates. At least I have found a quicker workaround here http://superuser.com/questions/376470/how-to-reinstall-grub2-efi All you have to do is booting from the grub menu the *buntu system you would like as the default one and run this command: sudo apt-get install --reinstall grub-efi-amd64 This might sounds obvious, but every time I was searching informations related to grub/uefi I always found instructions for external instruments such as boot-repair. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1056101 Title: grub-efi overwrites an existing grub*.efi file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1056101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1056101] Re: grub-efi overwrites an existing grub*.efi file
Discovered the same problem on Ubuntu 14.04 and 14.10. One of the worst thing is that a step of the installation (GRUB position in the mount point settings) is just broken and doesn't work properly with multi-boot systems. The last installed *buntu will be always set as the default system, even if you DON'T select /dev/sda for GRUB. After every installation I have to use BootRepair to set the system that I wanted as the default one. Other wise I can leave everything as it is, with a secondary system set as default, but at every kernel update there's the need to run the secondary system to run the update-grub command... As this bug seems to be quite old, I'm afraid that probably there isn't an easy solution. Is there at least a easier/faster workaround? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1056101 Title: grub-efi overwrites an existing grub*.efi file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1056101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318299] Re: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work
Before performing the reverse bisect process I thought to ask directly in the linux-acpi mailing list which was the patch (or the set of patches) that have fixed the acpi/backlight issue . This is the answer: (original message http://marc.info/?l=linux-acpim=140429106012604w=2) I think you will need at least: commit fbc9fe1b4f222a7c575e3bd8e9defe59c6190a04 Author: Aaron Lu aaron...@intel.com Date: Fri Oct 11 21:27:45 2013 +0800 ACPI / video: Do not register backlight if win8 and native interface exists commit 0e9f81d3b7cd0649a3bc437391b6a0650f98f844 Author: Aaron Lu aaron...@intel.com Date: Tue Feb 18 13:54:20 2014 +0800 ACPI / video: Add systems that should favour native backlight interface commit 751109aad5834375ca9ed0dcfcd85a00cbf872b5 Author: Rafael J. Wysocki rafael.j.wyso...@intel.com Date: Thu Jun 5 22:47:35 2014 +0200 ACPI / video: Change the default for video.use_native_backlight to 1 Maybe others, you will need to figure them out. I hope this will be helpful. Also, the first good working kernel is v3.16rc1. As long as I understand, instead of using a blacklist they have changed the default setup for the machines that are supporting Windows 8 with intel drivers. It seems that most of them don't use acpi. (More details starting from here http://lists.freedesktop.org/archives/intel- gfx/2013-October/034212.html) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318299 Title: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318299] Re: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work
Hi Christopher, in the last couple of days I tried the kernels I didn't try before and now I can tell for sure that the fix arrived with the v3.16rc1 kernel. I also had a look at the bisect documentation and tried to move my first steps. In the meantime Aaron Lu, the guy that was looking after the upstream bug-report, has answered my questions http://marc.info/?l=linux-acpim=140409199022683w=2 about a possible bug-fix for the previous kernels (especially the 13.3). He replied: No chance for v3.13 as it lacks other supporting bits, sorry. I've no skills to tell what it's better to do, but after Aaron's words I'm a bit afraid there will be a lot of work and still too many difficulties for the ubuntu-linux 3.13 bug-fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318299 Title: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318299] Re: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work
Some good news. I've tried the upstream kernel 3.16-rc2 and the brightness shortcut Fn+F6/Fn+F7 is now working out of the box without any workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318299 Title: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318299] Re: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work
Right, this should be OK http://marc.info/?l=linux- acpim=140178030214298w=2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318299 Title: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318299] Re: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work
** Attachment added: acpidump.txt https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299/+attachment/4124592/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318299 Title: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318299] Re: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work
@Christopher Here the bug report on the Linux mailing list: http://lkml.iu.edu//hypermail/linux/kernel/1406.0/00478.html hope it's OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318299 Title: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318299] Re: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work
** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-3.15-rc7 ** 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/1318299 Title: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318299] Re: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work
Hi Christopher, Tried the 3.15-rc7 kernel but the problem is still there. Pressing Fn+F6/Fn+F7 the brightness doesn't change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318299 Title: [Fujitsu Lifebook A512] Brightness hot keys Fn+F6/Fn+F7 don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318299] [NEW] Fujitsu Lifebook A512 - Brightness hot keys Fn+F6/Fn+F7 don't work out of the box
Public bug reported: (Fujitsu Lifebook A512 - Ubuntu 14.04 - Linux 3.13.0-24-generic x86_64) Pressing Fn+F6 or Fn+F7 the brightness doesn't change. WORKAROUND (found here http://ubuntuforums.org/showthread.php?t=2192471) 1) The command: for i in /sys/class/backlight/*; do echo $i;cat $i/brightness;cat $i/max_brightness;done shows this output: /sys/class/backlight/acpi_video0 1 100 /sys/class/backlight/intel_backlight 4882 4882 2) Then I've created the /usr/share/X11/xorg.conf.d/20-intel.conf file to set the intel_backlight interfece, with the following lines: Section Device Identifier card0 Driver intel Option Backlight intel_backlight BusID PCI:0:2:0 EndSection This makes the brightness shortcuts Fn+F6 and Fn+F7 work. EXTRA INFOS - I run ubuntu-bug linux on a new installation of the 14.04 in order to get informations of the original setup of the system. The workaround has been tried on another 14.04 installation on the same computer. - I didn't install any extra packages. Everything we need to make the hot keys Fn+F6/Fn+F7 work is already in the system. It seems to be a setup problem.. maybe related to backlight or xorg.. - The lines in /usr/share/X11/xorg.conf.d/20-intel.conf are just a copy/paste taken from the ubuntuforums.org topic. I've just tried to use it and luckily it worked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pinguinux 1731 F pulseaudio CurrentDesktop: Unity Date: Sun May 11 10:21:22 2014 HibernationDevice: RESUME=UUID=f6e9afa5-5b2f-4c3d-af00-aff1122b6fe6 InstallationDate: Installed on 2014-04-18 (22 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: FUJITSU LIFEBOOK A512 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=1cd50414-50f8-4f1c-9133-e7f3375c0415 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.16 dmi.board.name: FJNBB29 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.16:bd10/23/2013:svnFUJITSU:pnLIFEBOOKA512:pvr:rvnFUJITSU:rnFJNBB29:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A512 dmi.sys.vendor: FUJITSU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318299 Title: Fujitsu Lifebook A512 - Brightness hot keys Fn+F6/Fn+F7 don't work out of the box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249219] Re: 8086:0116 [Lenovo B570] backlight control acpi_video0 instead intel_backlight
Here the new bug related to Fujitsu Lifebook A512: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249219 Title: 8086:0116 [Lenovo B570] backlight control acpi_video0 instead intel_backlight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318299] Re: Fujitsu Lifebook A512 - Brightness hot keys Fn+F6/Fn+F7 don't work out of the box
** Description changed: (Fujitsu Lifebook A512 - Ubuntu 14.04 - Linux 3.13.0-24-generic x86_64) Pressing Fn+F6 or Fn+F7 the brightness doesn't change. - WORKAROUND (found here http://ubuntuforums.org/showthread.php?t=2192471) 1) The command: for i in /sys/class/backlight/*; do echo $i;cat $i/brightness;cat $i/max_brightness;done shows this output: /sys/class/backlight/acpi_video0 1 100 /sys/class/backlight/intel_backlight 4882 4882 2) Then I've created the /usr/share/X11/xorg.conf.d/20-intel.conf file to set the intel_backlight interfece, with the following lines: Section Device - Identifier card0 - Driver intel - Option Backlight intel_backlight - BusID PCI:0:2:0 + Identifier card0 + Driver intel + Option Backlight intel_backlight + BusID PCI:0:2:0 EndSection This makes the brightness shortcuts Fn+F6 and Fn+F7 work. - EXTRA INFOS - I run ubuntu-bug linux on a new installation of the 14.04 in order to get informations of the original setup of the system. The workaround has been tried on another 14.04 installation on the same computer. - - I didn't install any extra packages. Everything we need to make the hot keys Fn+F6/Fn+F7 work is already in the system. It seems to be a setup problem.. maybe related to backlight or xorg.. + - I didn't install any extra package. Everything we need to make the hot keys Fn+F6/Fn+F7 work is already in the system. It seems to be a setup problem.. maybe related to backlight or xorg.. - The lines in /usr/share/X11/xorg.conf.d/20-intel.conf are just a copy/paste taken from the ubuntuforums.org topic. I've just tried to use it and luckily it worked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.47 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: pinguinux 1731 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: pinguinux 1731 F pulseaudio CurrentDesktop: Unity Date: Sun May 11 10:21:22 2014 HibernationDevice: RESUME=UUID=f6e9afa5-5b2f-4c3d-af00-aff1122b6fe6 InstallationDate: Installed on 2014-04-18 (22 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: FUJITSU LIFEBOOK A512 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=1cd50414-50f8-4f1c-9133-e7f3375c0415 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.13.0-24-generic N/A - linux-backports-modules-3.13.0-24-generic N/A - linux-firmware 1.127 + linux-restricted-modules-3.13.0-24-generic N/A + linux-backports-modules-3.13.0-24-generic N/A + linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.16 dmi.board.name: FJNBB29 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.16:bd10/23/2013:svnFUJITSU:pnLIFEBOOKA512:pvr:rvnFUJITSU:rnFJNBB29:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A512 dmi.sys.vendor: FUJITSU -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318299 Title: Fujitsu Lifebook A512 - Brightness hot keys Fn+F6/Fn+F7 don't work out of the box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1249219] Re: backlight control acpi_video0 instead intel_backlight
On my Fujitsu Lifebook A512 I should be able to adjust the brightness pressing Fn+F6 or Fn+F7. The brightness-indicator pop-up works but the brightness doesn't change. This should be related to the cpi_video0 / intel_backlight issue. I found a workaround here http://ubuntuforums.org/showthread.php?t=2192471 Basically it works creating the /usr/share/X11/xorg.conf.d/20-intel.conf file with the following lines: Section Device Identifier card0 Driver intel Option Backlightintel_backlight BusID PCI:0:2:0 EndSection This makes the brightness shortcuts Fn+F6 and Fn+F7 work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1249219 Title: backlight control acpi_video0 instead intel_backlight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1249219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294027] Re: [Fujitsu LIFEBOOK A512] Touchpad scrolling and middle click doesn't work
At this stage a backport would make sense only to Ubuntu 12.04 LTS which is going to be supported till 2017. I don't use it but of course a backport could be useful for other people who are using the 12.04 and planned to use it til the EOL. I think it's up to the developers to take a decision. I'm not an expert and I have no idea if this is going to be a complicated job or not ;) Just in case! I've tried the psmouse-alps-1.3 workaround on a LIVE version of 12.04 and it works. So... at least if a backport to 12.04 would be difficult/problematic, we know that the workaround works also on 12.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294027 Title: [Fujitsu LIFEBOOK A512] Touchpad scrolling and middle click doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1294027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294027] Re: [Fujitsu LIFEBOOK A512] Touchpad scrolling and middle click doesn't work
Touchpad works out of the box on Ubuntu 14.04 with linux 3.13.0-20-generic This was the xinput output with the old kernel 3.13.0-19-generic: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ PS/2 Generic Mouseid=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] and now with 3.13.0-20-generic: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS GlidePoint id=13 [slave pointer (2)] ⎜ ↳ ALPS PS/2 Device Great! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294027 Title: [Fujitsu LIFEBOOK A512] Touchpad scrolling and middle click doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1294027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041916] Re: Touchpad of Fujitsu LifeBook AH532 not recognized
Just to let you know that the touchpad is now working properly on Lifebook A512 with Ubuntu 14.04 and linux 3.13.0-20-generic. I hope it will be the same on Lifebook AH532. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041916 Title: Touchpad of Fujitsu LifeBook AH532 not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1041916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294027] [NEW] xorg - alps touchpad
Public bug reported: As suggested here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1041916/comments/45 I run the ubuntu-bug xorg in orderd to get more infos related to bug Bug #1041916 about touchpad not working (scrolling and middle click left and right boutton pushed together) in Fujitsu LifeBook. The touchpad works properly after this workaround: 1- Downloaded drivers here http://www.dahetral.com/public-download/alps-psmouse-dlkm-for-3-2-and-3-5/view 2- Moved the folder psmouse-alps-1.3 into /usr/src/ 3- cd /usr/src 4- sudo dkms build psmouse/alps-1.3 5- sudo dkms install psmouse/alps-1.3 6- sudo rmmod psmouse sudo modprobe -v psmouse ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 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: Tue Mar 18 10:53:31 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: psmouse, alps-1.3, 3.11.0-18-generic, x86_64: installed psmouse, alps-1.3, 3.11.0-18-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:16c2] InstallationDate: Installed on 2014-03-17 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: FUJITSU LIFEBOOK A512 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic.efi.signed root=UUID=e71a3b11-0c9a-4e83-ade8-1a1090268bd1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.16 dmi.board.name: FJNBB29 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.16:bd10/23/2013:svnFUJITSU:pnLIFEBOOKA512:pvr:rvnFUJITSU:rnFJNBB29:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A512 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 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.5-1ubuntu2~saucy1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Tue Mar 18 10:43:53 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1427 vendor SAM xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1294027 Title: xorg - alps touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1294027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041916] Re: Touchpad of Fujitsu LifeBook AH532 not recognized
@Christopher M. Penalver (penalvch) Here we are: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1294027 Hope it's OK. Now I can describe the workaround, which might be helpful for other users: 1- Downloaded drivers here http://www.dahetral.com/public-download/alps-psmouse-dlkm-for-3-2-and-3-5/view 2- Moved the folder psmouse-alps-1.3 into /usr/src/ 3- cd /usr/src 4- sudo dkms build psmouse/alps-1.3 5- sudo dkms install psmouse/alps-1.3 6- sudo rmmod psmouse sudo modprobe -v psmouse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041916 Title: Touchpad of Fujitsu LifeBook AH532 not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1041916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1041916] Re: Touchpad of Fujitsu LifeBook AH532 not recognized
Had same problem on Lifebook A512 - Ubuntu 13.10 64bit and 14.04 Live version. The touchpad's scroll and mid-click (Left+Right button) were not working. I tried the commands suggested on #14 and this similar workaround http://nwoki.wordpress.com/2012/10/02/multitouch-fix-for-alps-touchpad Sorry, can't tell which one of the two methods worked, I'm totally noob with regard to kernel modules (made a lot of confiuson and receivde e few error messages)... anyway after a reboot I can tell that the touchpad is now working! This means that there must be something good into the psmouse-alps-1.3 driver (http://www.dahetral.com/public-download/alps-psmouse-dlkm- for-3-2-and-3-5/view) that could fix the problem. If there is any way to help to get more informations (run commands, post file settings...) just let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041916 Title: Touchpad of Fujitsu LifeBook AH532 not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1041916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283159] Re: Dash: no filters
The Dash has got filters again. (Unity 7.1.2+14.04.20140225) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283159 Title: Dash: no filters To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1283849] Re: LIM breaks middle click title bar
As previously reported on Bug #1282264, the middle click on the title bar still works when windows are maximised. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283849 Title: LIM breaks middle click title bar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1283849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 982434] Re: Opening the dash causes memory usage to climb dramatically, and never comes back down
Same story in Ubuntu 14.04 (Unity 7.1.2, Compiz 0.9.11, Intel card, RAM 2G) Opening the Dash will increase the memory usage of Compiz from 30 MiB to 90~100 MiB. The system and the applications are working fine. I didn't experienced any particular problem. just noticed compiz increasing the ram usage in the System monitor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/982434 Title: Opening the dash causes memory usage to climb dramatically, and never comes back down To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/982434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282264] [NEW] Middle-click on title bar doesn't work properly
Public bug reported: Middle-click on title bar should put a window behind all the others, but this happens only if a window is maximized. The mid-click on the title bar of a resized window, just doesn’t work. In dconf-editor the option Org → gnome → Desktop → wm → action-middle- click-titlebar is correctly set to 'lower'. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140218.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3 Uname: Linux 3.13.0-10-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Feb 19 21:45:48 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:150a] InstallationDate: Installed on 2014-02-17 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140217) MachineType: FUJITSU LIFEBOOK A530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-10-generic root=UUID=81fbf282-a456-4198-ad53-9557e7f58d72 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2010 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.17 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd12/03/2010:svnFUJITSU:pnLIFEBOOKA530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A530 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Feb 19 21:32:28 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 620 vendor LGD xserver.version: 2:1.15.0-1ubuntu6 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 third-party-packages trusty ubuntu ** Description changed: Middle-click on title bar should put a window behind all the others, but this happens only if a window is maximized. The mid-click on the title bar of a resized window, just doesn’t work. In dconf-editor the option Org → gnome → Desktop → wm → action-middle- - click-titlebar is regularly set to 'lower'. + click-titlebar is correctly set to 'lower'. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140218.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3 Uname: Linux 3.13.0-10-generic i686 .tmp.unity.support.test.0: - + ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Feb 19 21:45:48 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: - Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) -Subsystem: Fujitsu Limited. Device [10cf:150a] + Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) + Subsystem: Fujitsu Limited. Device [10cf:150a] InstallationDate: Installed on 2014-02-17 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140217) MachineType: FUJITSU LIFEBOOK A530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-10-generic root=UUID=81fbf282-a456-4198-ad53-9557e7f58d72 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2010 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.17 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias:
[Bug 1223928] Re: replace medibuntu with videolan archive for install-css
** Tags added: verification-done-raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1223928 Title: replace medibuntu with videolan archive for install-css To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdvdread/+bug/1223928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067812] Re: Gedit, blocked window at the corners with compiz grid plugin
Just upgraded compiz from quantal-proposed. Gedit is now working propperly with compiz grid plugin. Thanks, well done! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067812 Title: Gedit, blocked window at the corners with compiz grid plugin To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1067812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067812] [NEW] Gedit, blocked window at the corners with compiz grid plugin
Public bug reported: After that Gedit has been resized to one of the corners (shortcuts compiz grid plugin: Ctrl+Alt+Num_1/3/7/9) it's not possible to drag the window. Workaround: it's possible to move/drag the window again resizing the window half screen (combination Ctrl+Super+Left/Right Arrow). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: compiz 1:0.9.8.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Wed Oct 17 18:54:18 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Device [10cf:150a] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120918.1) MachineType: FUJITSU LIFEBOOK A530 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=eef3c104-f551-413f-9a85-ae54fa3d8973 ro quiet splash SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2010 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.17 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd12/03/2010:svnFUJITSU:pnLIFEBOOKA530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A530 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 quantal running-unity ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067812 Title: Gedit, blocked window at the corners with compiz grid plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1067812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063871] Re: Gedit, Nautilus will not snap/semi-maximize with the mouse
I have seen that the title and the description have been changed and now they includ Nautilus, but I didn't have any problem with Nautilus. On my installation it works fine with the grid plugin. I got this kind of problem only with Gedit. Talking about other programs I can only say that some applications (like System settings and Calculator) don't work at all with grid plugin. But I presume this is due to a particular setup, not really a bug. With these applications it's even not possible to resize the window.. to me it looks more like a feature.. well, I think so. In the meantime I have reported a new bug for the gedit grid corner problem: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1067812 Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063871 Title: Gedit, Nautilus will not snap/semi-maximize with the mouse To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1063871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1063871] [NEW] Problems with Gedit and Compiz Grid plugin
Public bug reported: The grid plugin is working with Gedit only using shortcuts. Trying to drag the top bar against the edges (like this http://www.youtube.com/watch?v=5w5OapWK2Xo) doesn't work. And also, after the window have been resized to the top or bottom corners (shortcuts Ctrl + Alt + Num_1 /3/7/9), then it will not be possible to drag the window. To move it again I need first to use the combination Ctrl+Super+Left/Right Arrow, to make the window half size of the screen, then I will be able to move/drag the window again. Can't tell if the problem is Gedit or Compiz. Till now I didn't experienced this problem with other programs, it appends only with Gedit (this is why I thought it could be a problem with Gedit.. but I can be wrong). I had the same problem on an installation of Ubuntu 12.10 and on a 12.10 Live version downloaded today (8 October 2012). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gedit 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Mon Oct 8 16:55:35 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120918.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1063871 Title: Problems with Gedit and Compiz Grid plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1063871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965895] Re: WiFi/NetworkManager menu doesn't show all items after booting into LiveCD environment
I have noticed the same situation on a installed and up to date version of Ubuntu 12.04 (32bit). Clicking the NetworkManager icon only four items were available. But after deactivating and then activating the Enable Wireless option, all the items were again available. I tried to log out and start a new session and also to reboot the system. Everything fine in both cases, the NetworkManager was still showing all the items. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965895 Title: WiFi/NetworkManager menu doesn't show all items after booting into LiveCD environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/965895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 841847] Re: Dash - unable to select multiple search filters within the same filter category simultaneously
I agree with #3 too. That could be the best solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/841847 Title: Dash - unable to select multiple search filters within the same filter category simultaneously To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/841847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 841847] Re: Dash - unable to select multiple search filters within the same filter category simultaneously
I have noticed this new behaviour and I was wondering whether this could be a bug or a new feature. Finally I found this page. I think this setup might be useful to search files, but it tends to be annoying with the Application lens. For instance if I'm watching the System category, then selecting the Games category all the softwares will be mixed together. This means every time you select a filter item you have to deselect the previous category. The app lens already requires many clicks (to open the category filter, to show all the results...) before reaching all the installed softwares in a category. This beaviour add a another step. I mean, a setup which result proper for one lens, might not be the best for another lens. Anyway... I presume I can't ask you to reintroduce this bug ;D Cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/841847 Title: Dash - unable to select multiple search filters within the same filter category simultaneously To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/841847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 876591] Re: Ctrl-Alt-KP_9 adjusts window to upper half instead of top right corner (behaves like Ctrl-Alt-KP_8)
@pitti Ctrl-Alt-KP_9 works now properly with the oneiric-proposed package on 11.10x86. Thanks! Still problems with the Ctrl-Alt-KP_4 and Ctrl-Alt-KP_6. The windows can be resized only half screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/876591 Title: Ctrl-Alt-KP_9 adjusts window to upper half instead of top right corner (behaves like Ctrl-Alt-KP_8) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-grid-plugin/+bug/876591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 565971] Re: I cannot mount my ipod shuffle. It shows up with the systemadministrationdisk utility; but it doesn't have any mountable partitions. (It actually does)
I confirm the bug on 10.04 and 11.04 with the old iPod Shuffle 512MB. Also, both the workarounds (removing libgpod-common or editing 90-libgpod.rules) are working. Has anyone experienced problems with iPod nano 5g after the 90-libgpod.rules workaround? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/565971 Title: I cannot mount my ipod shuffle. It shows up with the systemadministrationdisk utility; but it doesn't have any mountable partitions. (It actually does) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgpod/+bug/565971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs