Re: [Bug 1875240] Re: vbetool: mmap /dev/zero: Operation not permitted Failed to initialise LRMI (Linux Real-Mode Interface).
To assist with debugging please try both of these options (individually) from a clean state: (a) sudo mount -o remount,exec /dev (b) sudo setsebool -P mmap_low_allowed (ie. boot, test, reboot, test the other). Do either of those work? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875240 Title: vbetool: mmap /dev/zero: Operation not permitted Failed to initialise LRMI (Linux Real-Mode Interface). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vbetool/+bug/1875240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830379] Re: It is not clear how to install sources for the running kernel
** Description changed: On Ubuntu 18.04, with `apt-get source ` being the de facto way of getting (src-deb) sources for a binary package, it is not so with the linux kernel. `apt-get source linux-image-$(uname -r)` -- leads to "linux-signed" which is not the kernel src deb `apt-get source linux-image-generic` -- leads to "linux-meta" which is, again, not it `apt-get source linux` -- obtains the correct src deb but that's not transparent or obvious to new users and a deviation from the usual standard of using `apt-get source`. + + Prior discussion and background on #ubuntu-devel: + + * https://irclogs.ubuntu.com/2019/05/24/%23ubuntu-devel.html#t10:55 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830379 Title: It is not clear how to install sources for the running kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1830379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821610] Re: is openbve-data useful without openbve?
The new upstream maintainers are quite enthusiastically working to help get Openbve back into Debian/Ubuntu. If the data files hang around, it is likely to be less work later on: * https://github.com/leezer3/OpenBVE/issues/330#issuecomment-484102817 (The data files can be used with other engines; eg. the freeware-no- source BVE Trainsim running under Wine). ** Bug watch added: github.com/leezer3/OpenBVE/issues #330 https://github.com/leezer3/OpenBVE/issues/330 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821610 Title: is openbve-data useful without openbve? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openbve-data/+bug/1821610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56459] Re: Unix putty does not accept user@host syntax
Excellent, Jacob! Thanks for keeping tabs on it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/56459 Title: Unix putty does not accept user@host syntax To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/putty/+bug/56459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574534] Re: Aspect ratio of Ubuntu Mono font at small sizes changed
** Changed in: fonts-ubuntu (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574534 Title: Aspect ratio of Ubuntu Mono font at small sizes changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-ubuntu/+bug/1574534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794318] BIOS shows RAID1, newer mdadm --detail-platform does not
https://irclogs.ubuntu.com/2018/09/27/%23ubuntu-devel.html#t11:31 The BIOS shows a RAID1 (mirror) pair, this is designated as: RAID Level: "Recovery (Cont.)" in the BIOS. (screenshot) This stands for "Recovery Set" == RAID1/Mirror group. Newer 'mdadm --detail-platform' only reports: $ sudo mdadm --examine /dev/sd[ab] Platform : Intel(R) Rapid Storage Technology Version : 12.9.0.2006 RAID Levels : raid0 the expected output would instead be: "RAID Levels : raid0 raid1 raid10 raid5" However, the version of 'mdadm' used to actually boot + configure the system is the older version. It is still necessary to get the output of 'mdadm --detail-platform' from the working version in the initramfs. This is because the version use on bootup is the one in the initramfs (working) and the one here us on the main root filesystem (non-working). There are various other complications on this machine: 1. Gaming laptop with the BIOS detail not properly populated: MSI Gaming Notebook GS70 2QE-046NL 17.3", 4710HQ, 1.5TB, GTX970M 2. Other (non-RAIDed, non-SSD) disks on the same controller 3. Apparently a BIOS update at some point. All of these need testing/eliminating. Reporter has indicated they are not available for several hours. -Paul -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794318 Title: unable to boot after installing vagrant To manage notifications about this bug go to: https://bugs.launchpad.net/vagrant/+bug/1794318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794318] Not kernel, mdadm initramfs
TL;DR: probably mdadm commit from April 2018; see end. Today's IRC logs of debugging session with reporter: https://irclogs.ubuntu.com/2018/09/26/%23ubuntu-devel.html#t06:41 Current understanding of the situation from log analysis: 08:21 reboot with (4.15.0-29.31-generic), no problem 08:21 apt-get --no-upgrade -o Acquire::gpgv::Options::=--ignore-time-conflict -y install grub-efi-amd64-signed 08:22 apt-get --no-upgrade -o Acquire::gpgv::Options::=--ignore-time-conflict -y install shim-signed 08:23 apt upgrade 08:30 reboot with (4.15.0-34.37-generic), no problem 08:35 sudo apt-get install vagrant -y && sudo reboot Setting up mdadm (4.1~rc1-3~ubuntu18.04.1) ... Setting up reiserfsprogs (1:3.6.27-2) ... Setting up lvm2 (2.02.176-4.1ubuntu3) ... Setting up xfsprogs (4.9.0+nmu1ubuntu2) ... Setting up xfsprogs (4.9.0+nmu1ubuntu2) ... update-initramfs: deferring update (trigger activated) [all above] Processing triggers for initramfs-tools (0.130ubuntu3.3) ... update-initramfs: Generating /boot/initrd.img-4.15.0-34-generic ~08:37, reboot to (4.15.0-34.37-generic), fails, no syslog saved "IMSM RAID geometry validation failed." (screenshot) "platform does not support raid1 with 2 disks" (screenshot) 08:38, reboot to (4.15.0-29.31-generic) [manually in Grub] 08:59, reboot to (4.15.0-29.31-generic) [manually in Grub] So, not the kernel. But something that (most likely) mdadm changed in the copy of mdadm copied into the regenerated 'initramfs'. Probably running "mdadm --assemble --scan" should also produce the same message. Both kernels booted fine prior to the mdadm update fetched via the 'apt-get install vagrant'. That brings us to mdadm, looking at the master branch, there was a commit just prior to the calculation code that generates the "IMSM RAID geometry validation failed" message: https://www.spinics.net/lists/raid/msg60747.html https://github.com/neilbrown/mdadm/commit/fcc2c9daede11fcc67e4032fd6fa8da198aaa319#diff-d9ce63e82fa010385c80834480624fa4L7736 RAID 1 is mirroring. The second message "platform does not support raid1 with 2 disks" might well suggest something is non-function. Reporter has indicated they are not available for several hours, so further investigation will likely have to wait. -Paul -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794318 Title: unable to boot after installing vagrant To manage notifications about this bug go to: https://bugs.launchpad.net/vagrant/+bug/1794318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794318] Which kernel?
Per the earlier conversation: https://irclogs.ubuntu.com/2018/09/25/%23ubuntu-devel.html#t09:22 need to know: * exact version number of last working Linux kernel * exact version number of non-working Linux kernel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794318 Title: kernel update breaks boot on intel fake raid 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"
The valid CSS would be: font-weight: lighter; In the case of explicitly wanting "Ubuntu Light", once everything is fixed, the CSS access will hopefully be just: font-family: "Ubuntu"; font-weight: 300; -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512111 Title: "Ubuntu Light" font has heavier weight than "Ubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1512111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"
Hello Daniel, plan is to switch the fonts for source-built versions. These source-built fonts should in the first instance be work-alikes (equivalents) to the binary fonts currently shipped via Google Fonts. The versions hosted on Google Fonts have undergone various refinements of the metadata via binary patching. The intention is that the source-built version will have equivalent metadata. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512111 Title: "Ubuntu Light" font has heavier weight than "Ubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1512111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
Christian: looking back and your reply in #478, it would appear that you're on Mint, not Ubuntu. It is likely the case that Mint is still shipping the buggy kernel(s). We can see in #478: "When installing the Kernels provided above, I can again do changes in BIOS and they stay over reboot. However as soon as I revert back to 4.13.0-21 Kernel, the Problem is back." ...Which is exactly what would be expected. The solution is, after unlocking the flash, do not run a buggy that will relock it. -- 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: corrupted BIOS due to Intel SPI bug in kernel 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 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
@Paul sabret00the. Please can you file separate new bugs for the "disassociated with its launcher icon", "my swap disk has issues", and "I can't launch any Virtual Boxes". These are not related to the CMP bit in the flash chip, and putting them on this bug report adds confusion to this issue which is being worked on. -- 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: corrupted BIOS due to Intel SPI bug in kernel 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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models
Register map documentation for the SPI (Serial Peripheral Interface) in recent Intels begins on page 5626 https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/atom-z8000 -datasheet-vol-2.pdf HSFSTS (Hardware Sequencer Status) + HSFCTL (Hardware Sequencer Control) are covered on the following pages. The 'intel-spi' driver accesses both of these together, treating them as a single 32-bit register (HSFSTS_CTL). --- PS. For those watching this bug, and wondering about what whatelse is going on in the background. Yes there is, eg. per #ubuntu-devel yesterday, today should be a visit to hardware manufacture (ODM), to try out some suggestions received via Intel: https://irclogs.ubuntu.com/2017/12/20/%23ubuntu-devel.html#t16:38 -- 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/ubuntu/+source/linux/+bug/1734147/+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
** Description changed: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY The bug also affects: Acer Aspire E5-771G Acer TravelMate B113 + Toshiba Satellite S55T-B5233 --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- Architecture: amd64 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- -- 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/ubuntu/+source/linux/+bug/1734147/+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
Could somebody with the hardware also do a test with the following lines commented out in 'intel-spi.c', commenting out the writel() that disables SMI interrupt generation, re-compile the kernel and retest: https://github.com/torvalds/linux/blob/8afda8b26d01ee26a60ef2f0284a7f01a5ed96f8/drivers/mtd /spi-nor/intel-spi.c#L324 /* Disable #SMI generation */ val = readl(ispi->base + HSFSTS_CTL); val &= ~HSFSTS_CTL_FSMIE; writel(val, ispi->base + HSFSTS_CTL); // comment out this line (hardware sequencer) and: https://github.com/torvalds/linux/blob/8afda8b26d01ee26a60ef2f0284a7f01a5ed96f8/drivers/mtd /spi-nor/intel-spi.c#L354 /* Disable #SMI generation from SW sequencer */ val = readl(ispi->sregs + SSFSTS_CTL); val &= ~SSFSTS_CTL_FSMIE; writel(val, ispi->sregs + SSFSTS_CTL); // comment out this line (software sequencer) ** Description changed: SRU Justification Impact: Many users are reporting issues with bios corruption with 17.10. This seems to stem from enabling the intel-spi-* drivers in the kernel, which don't appear to be ready for use on end-user machines. Fix: Disable this driver. Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Hi all, Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after rebooting, the system starts with the old settings. Moreover (and most important) USB booting is not possible anymore since USB is not recognized. It's very serious, since our machines do not have a CDROM. Lenovo forums at the moment are full of topics regading this issue. Thank you!! UPDATE (01/12/2017) LENOVO machines affected so far (please add your affected model to this list): Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY - The bug also affects Acer Aspire E5-771G. + The bug also affects: + Acer Aspire E5-771G + Acer TravelMate B113 --- Temporary workaround: https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t -Save-Settings-Or-Exit/m-p/3853208#M157885 --- result from apport-collect 1734147: --- - ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: tob1608 F pulseaudio - /dev/snd/controlC0: tob1608 F pulseaudio - CurrentDesktop: ubuntu:GNOME - DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-22 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20378 - Package: linux (not installed) - ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 RelatedPackageVersions: linux-restricted-modules-4.13.0-17-generic N/A linux-backports-modules-4.13.0-17-generic N/A linux-firmware 1.169 Tags: artful wayland-session Uname: Linux 4.13.0-17-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo - _MarkForUpload: True dmi.bios.date: 08/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN43WW(V3.03) - dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: Not Defined - dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.family: IDEAPAD dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO --- -- 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/ubuntu/+source/linux/+bug/1734147/+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
Mika Westerberg emailed again with a pointer to the commit from a few months ago, specifically dealing with a similar issue on Lenovo Yoga machines: """ mfd: lpc_ich: Do not touch SPI-NOR write protection bit on Haswell/Broadwell At least on Lenovo Thinkpad Yoga, the BIOS seems to monitor the SPI-NOR write protection bit and if it is flipped to read/write it assumes the BIOS configuration was changed on next reboot. It then, for unknown reasons, resets the BIOS settings back to default. We can prevent this by just leaving the write protection bit intact and let the SPI-NOR driver know whether the device is writable or not. In case of this particular Lenovo the SPI-NOR flash will be exposed as read-only. """ https://github.com/torvalds/linux/commit/d9018976cdb6eefc62a7ba79a405f6c9661b08a7 So, if the driver is disabled (such that it does not load), and two full reboots are performed afterwards. Is it then possible (on the third reboot) to make changes to the BIOS boot order again? -- 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/ubuntu/+source/linux/+bug/1734147/+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
(For clarity the above upload of linux (kernel)=4.13.0-21.24) is a workaround that just disables compiling in of the module under suspicion. Because the module is not compiled it, it will not therefore be loaded either). -- 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/ubuntu/+source/linux/+bug/1734147/+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
[The two theories provided by Mika Westerberg, verbatim] """ Instead I have a theory since as far as I know there have been to kinds of issues. 1. Flash is left locked. This makes the BIOS impossible to save settings. This seems to happen only for GigaDevice flashes and for all of those there is this flag in "spi-nor.c" set: SPI_NOR_HAS_LOCK. Normally Linux only reads JEDEC ID of the chip and nothing else. However, in this case it may be possible that Linux does unlock + operation + lock which leaves the flash locked and confuses BIOS. 2. Flash corrupted We've seen once on Apollo Lake systems where the BIOS image had configured to use Quad mode instead of Single but the chip was connected only with single data lane or so. Trying to access the flash using HW sequencer then does damage to the chip because it is in wrong mode. This only happened with certain Winbond chips. In any case it would require some more analysis to find the root cause. """ -- 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/ubuntu/+source/linux/+bug/1734147/+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
Have received an excellent reply from Mika Westerberg (thank you!). One with a suggestion regarding 'GigaDevice' flash chips, and one regarding certain 'Winbond' flash chips. Is somebody with access or one of more of these machine(s) able to provide insight into what flash parts are in their machine? -- 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/ubuntu/+source/linux/+bug/1734147/+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
Page 5 of: http://opensecuritytraining.info/IntroBIOS_files/Day2_03_Advanced%20x86%20-%20BIOS%20and%20SMM%20Internals%20-%20SPI%20Flash%20Protection%20Mechanisms.pptx Talks about "Flash Protection Mechanism"; "Write Protect / Writes blocked / Not Range Specific / SMI# override: Same as Write Protect in previous ICHs for FWH" "Applies to the entire flash chip (Global Flash Protection)" "Provides SMM the ability to determine whether or not a request to unlock the BIOS flash for writing will be permitted" So possibly a situation where the writes are being marshalled to go via the System Management Mode, where there is lack of correct code there to handle it. (Or the opposite). [Or I could be barking up completely the wrong tree] -- 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/ubuntu/+source/linux/+bug/1734147/+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
I've emailed Mika Westerberg (author of the module) to ask to share anything further documentation they've got that would allow a better understanding of the (intended) operation of the 'intel-spi' module. -- 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/ubuntu/+source/linux/+bug/1734147/+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
FWIW, the Intel-SPI Readme contains: https://github.com/torvalds/linux/blob/master/Documentation/mtd/intel- spi.txt "makes it possible to read and write the SPI serial flash, if certain protection bits are not set and locked." "… If it finds any of them set, the whole MTD device is made read-only to prevent partial overwrites." Corresponding code is in: https://github.com/torvalds/linux/blob/8afda8b26d01ee26a60ef2f0284a7f01a5ed96f8/drivers/mtd /spi-nor/intel-spi.c >From a casual read, the "Disable #SMI generation" code (once using the hardware sequencer, and once using the software sequencer) stands out, because there is no reverse action and is one-way. This code is within the 'intel_spi_init()' routine, and if it is the cause, might explain which the problem shows up merely by loading the module, when _init() is called. -- 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/ubuntu/+source/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 412503] Re: OpenBve+Class 323 does not support plugin DLLs on Linux
Aidan: I think I made the code to make it work. From what I recall the main upstream author is/was not happy with the just API compatibility (recompiling) and would have preferred to see an ABI compatible (binary compatibility). This effectively means the need for a full i386+Win32 environment which means Wine. I was strongly requested not to apply, and so in my time, I didn't apply it. But, yes, the concept and working code should still be there, and I expect could be made to function again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/412503 Title: OpenBve+Class 323 does not support plugin DLLs on Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bve-train-br-class-323/+bug/412503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
This changeset was applied upstream: https://www.virtualbox.org/changeset/62201/vbox/trunk/src/VBox/Additions/common/crOpenGL/egl.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
Further discussion at:
https://irclogs.ubuntu.com/2016/07/12/%23ubuntu-devel.html#t15:20
with a pointer to:
https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Additions/common/crOpenGL/egl.c#L136
And side-discussion of possible better ways of how to detect client GL
vs. server GL, which at the moment is using:
getenv("DISPLAY") != NULL
and a quick look into how the Nvidia driver packaging is handling this
in postinst using:
update-alternatives --force --install /etc/ld.so.conf.d/x86_64-linux-
gnu_GL.conf x86_64-linux-gnu_gl_conf /usr/lib/nvidia-361/ld.so.conf 8604
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1599775
Title:
"low-graphics mode" in VirtualBox guest, but X server running
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
@ellisistfroh: I cannot see anything in the lightdm (1.18.2-0ubuntu1) changelog to suggest that it might have addressed this issue. @michael-thayer: thank you for spending the extra time to confirm that lightdm (1.18.2-0ubuntu1) is still affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599775] Re: "low-graphics mode" in VirtualBox guest, but X server running
** Description changed: I sometimes get the "low-graphics mode" message when starting an Ubuntu 16.04 virtual machine inside of VirtualBox (current development code trunk, somewhere past version 5.1 beta 3 and a debug build). When I switch to VT-7 I find the X server running without any visible issues (I am the upstream developer of the guest graphics drivers, so I have a reasonable but not infallible understanding of the X server). The virtual machine has Guest Additions installed, same vintage and also a debug build. Two screens are enabled as is 3D acceleration. The host system is also Ubuntu 16.04. I am still trying to work out what triggers the message, but in my last attempts a cold boot failed to produce it, while a clean reboot did, but only when the host system was not under load (under load as in building VirtualBox). Searching the lightdm log files led me to the message "CRITICAL **: session_get_login1_session_id: assertion 'session != NULL' failed", which in turn led me to this similar-looking Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814760 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 7 10:49:27 2016 InstallationDate: Installed on 2016-06-08 (28 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) + + IRC discussion at: + + https://irclogs.ubuntu.com/2016/07/07/%23ubuntu-devel.html#t07:52 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599775 Title: "low-graphics mode" in VirtualBox guest, but X server running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1599775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573275] Re: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom'
Alternative solution implemented via Open Build Service 'Ubuntu:16.04' configuration update. ** Changed in: ifupdown (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573275 Title: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573275] Re: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom'
So, guessing, was this the diff that was applied: --- Ubuntu-16.04.txt.orig 2016-04-22 14:24:12.163974719 +0200 +++ Ubuntu-16.04.txt2016-04-22 14:23:51.095974821 +0200 @@ -88,2 +88,3 @@ +Ignore: upstart:ifupdown Ignore: aaa_base:aaa_skel,suse-release,logrotate,ash,mingetty,distribution-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573275 Title: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573275] Re: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom'
Neal: do you have eg. an OBS commit log/changeset we can link this to? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573275 Title: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1573275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572588] Re: Toolkit should use new orange #e95420
** Summary changed: - does not use the new orange + Toolkit should use new orange #e95420 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572588 Title: Toolkit should use new orange #e95420 To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-sprint/+bug/1572588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573275] Re: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom'
** Description changed: '/etc/init.d/networking' for 'ifupdown' starts with: # Required-Start:mountkernfs $local_fs urandom it would appear that 'mountkernfs' and 'urandom' are not hard- dependencies, and their presence prevents successful installation in - virtual machines in some circumstances. This was reported by Conan - Kudo/ on #ubuntu-devel whilst working on support for Suse + virtual machines in some circumstances. This was reported by Neal + Gompa/ on #ubuntu-devel whilst working on support for Suse Open Build System (OBS) to build Xenial packages: http://changelogs.ubuntu.com/changelogs/pool/main/i/ifupdown/ifupdown_0.8.10ubuntu1/changelog Full and snipped output logs are at: http://paste.fedoraproject.org/358318/61266534/ https://paste.fedoraproject.org/358315/66065146/ in particular: [ 530s] [239/256] installing ifupdown-0.8.10ubuntu1 [ 530s] Creating /etc/network/interfaces. [ 531s] insserv: Service mountkernfs has to be enabled to start service networking [ 531s] insserv: Service urandom has to be enabled to start service networking [ 531s] insserv: exiting now! [ 531s] update-rc.d: error: insserv rejected the script header [ 531s] dpkg: error processing package ifupdown (--install): [ 531s] subprocess installed post-installation script returned error exit status 1 The reporter tested that commenting out 'mountkernfs' and 'urandom' allowed the ifupdown '/etc/init.d/networking' init-script to successfully complete. Ideally a hard-dependency should not be declared if it is not actually a hard-dependency, and introduces a regression by preventing successfully installation in circumstances that are reported to have worked previously for installing earlier Debian/Ubuntu versions on OBS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573275 Title: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1573275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573275] Re: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom'
** Description changed: '/etc/init.d/networking' for 'ifupdown' starts with: - # Required-Start:mountkernfs $local_fs urandom + # Required-Start:mountkernfs $local_fs urandom it would appear that 'mountkernfs' and 'urandom' are not hard- dependencies, and their presence prevents successful installation in virtual machines in some circumstances. This was reported by Conan Kudo/ on #ubuntu-devel whilst working on support for Suse Open Build System (OBS) to build Xenial packages: http://changelogs.ubuntu.com/changelogs/pool/main/i/ifupdown/ifupdown_0.8.10ubuntu1/changelog Full and snipped output logs are at: - http://paste.fedoraproject.org/358318/61266534/ - https://paste.fedoraproject.org/358315/66065146/ + http://paste.fedoraproject.org/358318/61266534/ + https://paste.fedoraproject.org/358315/66065146/ in particular: - [ 530s] [239/256] installing ifupdown-0.8.10ubuntu1 - [ 530s] Creating /etc/network/interfaces. - [ 531s] insserv: Service mountkernfs has to be enabled to start service networking - [ 531s] insserv: Service urandom has to be enabled to start service networking - [ 531s] insserv: exiting now! - [ 531s] update-rc.d: error: insserv rejected the script header - [ 531s] dpkg: error processing package ifupdown (--install): - [ 531s] subprocess installed post-installation script returned error exit status 1 - - The reporter tested that commenting out 'mountkernfs' and 'urandom' allowed the ifupdown '/etc/init.d/networking' init-script to successfully complete. + [ 530s] [239/256] installing ifupdown-0.8.10ubuntu1 + [ 530s] Creating /etc/network/interfaces. + [ 531s] insserv: Service mountkernfs has to be enabled to start service networking + [ 531s] insserv: Service urandom has to be enabled to start service networking + [ 531s] insserv: exiting now! + [ 531s] update-rc.d: error: insserv rejected the script header + [ 531s] dpkg: error processing package ifupdown (--install): + [ 531s] subprocess installed post-installation script returned error exit status 1 + + The reporter tested that commenting out 'mountkernfs' and 'urandom' + allowed the ifupdown '/etc/init.d/networking' init-script to + successfully complete. Ideally a hard-dependency should not be declared if it is not actually a hard-dependency, and introduces a regression by preventing successfully - installation in circumstances and are reported to have worked before. + installation in circumstances that are reported to have worked + previously for installing earlier Debian/Ubuntu versions on OBS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573275 Title: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1573275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573275] [NEW] ifupdown should not hard-depend upon 'mountkernfs' and 'urandom'
Public bug reported: '/etc/init.d/networking' for 'ifupdown' starts with: # Required-Start:mountkernfs $local_fs urandom it would appear that 'mountkernfs' and 'urandom' are not hard- dependencies, and their presence prevents successful installation in virtual machines in some circumstances. This was reported by Conan Kudo/ on #ubuntu-devel whilst working on support for Suse Open Build System (OBS) to build Xenial packages: http://changelogs.ubuntu.com/changelogs/pool/main/i/ifupdown/ifupdown_0.8.10ubuntu1/changelog Full and snipped output logs are at: http://paste.fedoraproject.org/358318/61266534/ https://paste.fedoraproject.org/358315/66065146/ in particular: [ 530s] [239/256] installing ifupdown-0.8.10ubuntu1 [ 530s] Creating /etc/network/interfaces. [ 531s] insserv: Service mountkernfs has to be enabled to start service networking [ 531s] insserv: Service urandom has to be enabled to start service networking [ 531s] insserv: exiting now! [ 531s] update-rc.d: error: insserv rejected the script header [ 531s] dpkg: error processing package ifupdown (--install): [ 531s] subprocess installed post-installation script returned error exit status 1 The reporter tested that commenting out 'mountkernfs' and 'urandom' allowed the ifupdown '/etc/init.d/networking' init-script to successfully complete. Ideally a hard-dependency should not be declared if it is not actually a hard-dependency, and introduces a regression by preventing successfully installation in circumstances that are reported to have worked previously for installing earlier Debian/Ubuntu versions on OBS. ** Affects: ubuntu Importance: Medium Status: Confirmed ** Tags: regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573275 Title: ifupdown should not hard-depend upon 'mountkernfs' and 'urandom' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1573275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"
(For want of a better place to put it), useful ttx diffs + changelog forwarded to me at the end of yesterday which gives more context on what the above referenced .zip file delivery is. [Kudos to DM Engineering to doing this in an automated fashion, and those along the chain for passing it along]. ** Attachment added: "ttx diffs + changelog" https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1512111/+attachment/4545120/+files/2015-12-10_Ubuntu_0.831%20Engineering%20notes%20and%20Patches.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1512111 Title: "Ubuntu Light" font has heavier weight than "Ubuntu" To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1512111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066963] Re: Dash - Update the Dash to use the Ubuntu medium font weight
I received a 'Ubuntu_0.831.zip' file yesterday, without any context, but appears to a possible test case[1] that if applied to the main font build would unblock this and allow Dash to select Medium (hopefully; other blocker was in Qt). [1] (Selected font test, probably for confirmation of that the decoupling of Light/Medium and fixing of the Postscript-Name for compliance). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066963 Title: Dash - Update the Dash to use the Ubuntu medium font weight To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1066963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"
The test case suggests a change to 'Ubuntu Mono', but the
'Ubuntu_0.831.zip' I have here doesn't have any Ubuntu Mono (nor source,
nor changelog, nor scripting, nor test cases, nor any contextual
information). I can see:
2016-01-04 11:31 Zip file (repacked today?)
2015-12-04 10:55 .ttfs
2015-12-04 10:53:12..10:53:39, internal timestamps (three-second intervals)
The two positive takeaways are that the version debug glyph shows 0.831,
and from the close-interval timestamps we can deduce that the change(s)
were made in an automated fashion. The question remains *what those
changes are*.
We can see eg:
$ otfinfo -s {,/usr/share/fonts/truetype/ubuntu-font-
family/}Ubuntu-R.ttf
That the 0.84 files already out in the real world have flags indicating
'Hebrew' and 'Default', which these don't. Since these support less
than than the higher-numbered version out there, it remains:
* What are these files for. What is their purpose, what is supposed to be
tested.
* Are they even targetted for distribution. If so what are we supposed to do
with them when they have a lower version number and less functionality.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1512111
Title:
"Ubuntu Light" font has heavier weight than "Ubuntu"
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1512111/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 861334] Re: [nc] Ship Ubuntu Mono .psf as default console font in Ubuntu 11.10
If other people want to test: sudo apt-get install fonts-ubuntu-font-family-console dpkg -L fonts-ubuntu-font-family-console | grep -m1 .psf | xargs sudo setfont -C /dev/tty2 and then it's possible to flick between: Ctrl-Alt-F1 (tty1 showing Ubuntu Mono Regular rendered to 8x16) Ctrl-Alt-F2 (tty2 showing default: Terminus) Ctrl-Alt-F7 (GUI desktop) The hinting information is used for generation of the bitmaps, but it's pretty sub-optimal. Rather than attempt to improve the hinting just to export to a bitmap …it would probably be faster/more efficient to take the Ubuntu Mono design principles and hunt and peck pixels in a bitmap editor as everyone did in the 1990s. This would then not be derived either, and so with a BSD/MIT/PD licence it could be built to fall back on existing Terminus and so provide both useful coverage and the slight variations of the 'i' 'l', 'm' for the look and feel (because of the limited number of pixels most glyphs in terminal tend towards looking the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/861334 Title: [nc] Ship Ubuntu Mono .psf as default console font in Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/861334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525150] Re: Ubuntu font missing part of 8 and 3 in hexchat
Possibly from the numeral glyphs being fetched from Ubuntu Arabic Regular, and the Latin coming from Ubuntu Regular, and the metrics somehow being confused. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525150 Title: Ubuntu font missing part of 8 and 3 in hexchat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1525150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519393] Re: New revision of 0c45:8419 Microdia/Wivitouch USB Infrared Touchscreen no longer working under 14.04
** Description changed: Filing here per request at: http://irclogs.ubuntu.com/2015/11/24/%23ubuntu-devel.html#t14:35 - The issue is regarding touch infra-red overlay touch screen panels from + The issue is regarding infra-red overlay touch screen panels from Wivitouch in China: - http://www.wivitouch.com/sdp/1079694/4/pd-5199630/7116924-2132434/Multitouch_screen_infrared_touch_screen_19.html - http://www.diytrade.com/china/pd/7116927/Multitouch_screen_infrared_touch_screen_18_5.html - http://img.diytrade.com/smimg/1079694/17764824-1256906-0/nn/58f1.jpg + http://www.wivitouch.com/sdp/1079694/4/pd-5199630/7116924-2132434/Multitouch_screen_infrared_touch_screen_19.html + http://www.diytrade.com/china/pd/7116927/Multitouch_screen_infrared_touch_screen_18_5.html + http://img.diytrade.com/smimg/1079694/17764824-1256906-0/nn/58f1.jpg I have approximately 300 USB touch panels, from two different batches, but all report the same USB ID 0c45:8419. The manufacturer told me they had changed the firmware without changing the USB ID/version because they did not consider the change important. Both batches work correctly on Ubuntu 10.04, but only the first batch works on 14.04. The remaining batch does not so this is a regression. After plugging in, both batches appear equivalently under: /dev/input/eventNN and for both 'evtest' reports: Input device ID: bus 0x3 vendor 0xc45 product 0x8419 version 0x100 Input device name: "SONiX USB Device" … Presumably something is occuring that causes a version version of 'libev' to handle one batch differently. Attached is the output of running: $ sudo lsusb - -c -d 0c45:8419 > ….txt for one device from each of the two batches, which confirms that they appear identically. I have tested 250/250 (working) from the first batch, and 10/50 (not-working) from the second batch. The only way to tell the batches apart is by the length of the USB cable, the first (working) batch have USB cables that are 15-20 centimetres long, and the second (non-working) batch have USB cables that are ~1 metre long. ** Description changed: Filing here per request at: http://irclogs.ubuntu.com/2015/11/24/%23ubuntu-devel.html#t14:35 The issue is regarding infra-red overlay touch screen panels from Wivitouch in China: http://www.wivitouch.com/sdp/1079694/4/pd-5199630/7116924-2132434/Multitouch_screen_infrared_touch_screen_19.html http://www.diytrade.com/china/pd/7116927/Multitouch_screen_infrared_touch_screen_18_5.html http://img.diytrade.com/smimg/1079694/17764824-1256906-0/nn/58f1.jpg I have approximately 300 USB touch panels, from two different batches, but all report the same USB ID 0c45:8419. The manufacturer told me they had changed the firmware without changing the USB ID/version because they did not consider the change important. Both batches work correctly - on Ubuntu 10.04, but only the first batch works on 14.04. The remaining - batch does not so this is a regression. + on Ubuntu 10.04, but only the first batch works on Ubuntu 14.04. The + remaining batch does not work under Ubuntu 14.04 so this is a + regression. After plugging in, both batches appear equivalently under: /dev/input/eventNN and for both 'evtest' reports: Input device ID: bus 0x3 vendor 0xc45 product 0x8419 version 0x100 Input device name: "SONiX USB Device" … Presumably something is occuring that causes a version version of 'libev' to handle one batch differently. Attached is the output of running: $ sudo lsusb - -c -d 0c45:8419 > ….txt for one device from each of the two batches, which confirms that they appear identically. I have tested 250/250 (working) from the first batch, and 10/50 (not-working) from the second batch. The only way to tell the batches apart is by the length of the USB cable, the first (working) batch have USB cables that are 15-20 centimetres long, and the second (non-working) batch have USB cables that are ~1 metre long. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519393 Title: New revision of 0c45:8419 Microdia/Wivitouch USB Infrared Touchscreen no longer working under 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evtest/+bug/1519393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519393] Re: New revision of 0c45:8419 Microdia/Wivitouch USB Infrared Touchscreen no longer working under 14.04
** Description changed: Filing here per request at: http://irclogs.ubuntu.com/2015/11/24/%23ubuntu-devel.html#t14:35 - I have approximately 300 USB touch panels. These are from two different - batches, but all report the same USB ID 0c45:8419. The manufacturer - told me they had changed the firmware without changing the USB - ID/version because they did not consider the change important. Both - batches work correctly on Ubuntu 10.04, but only the first batch works - on 14.04. The remaining batch does not so this is a regression. + The issue is regarding touch infra-red overlay touch screen panels from + Wivitouch in China: + + http://www.wivitouch.com/sdp/1079694/4/pd-5199630/7116924-2132434/Multitouch_screen_infrared_touch_screen_19.html + http://www.diytrade.com/china/pd/7116927/Multitouch_screen_infrared_touch_screen_18_5.html + http://img.diytrade.com/smimg/1079694/17764824-1256906-0/nn/58f1.jpg + + I have approximately 300 USB touch panels, from two different batches, + but all report the same USB ID 0c45:8419. The manufacturer told me they + had changed the firmware without changing the USB ID/version because + they did not consider the change important. Both batches work correctly + on Ubuntu 10.04, but only the first batch works on 14.04. The remaining + batch does not so this is a regression. After plugging in, both batches appear equivalently under: /dev/input/eventNN and for both 'evtest' reports: Input device ID: bus 0x3 vendor 0xc45 product 0x8419 version 0x100 Input device name: "SONiX USB Device" … Presumably something is occuring that causes a version version of 'libev' to handle one batch differently. Attached is the output of running: $ sudo lsusb - -c -d 0c45:8419 > ….txt for one device from each of the two batches, which confirms that they appear identically. I have tested 250/250 (working) from the first batch, and 10/50 (not-working) from the second batch. The only way to tell the batches apart is by the length of the USB cable, the first (working) batch have USB cables that are 15-20 centimetres long, and the second (non-working) batch have USB cables that are ~1 metre long. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519393 Title: New revision of 0c45:8419 Microdia/Wivitouch USB Infrared Touchscreen no longer working under 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evtest/+bug/1519393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519393] Re: New revision of 0c45:8419 Microdia USB Touchscreen not working under 14.04
** Description changed: Filing here per request at: http://irclogs.ubuntu.com/2015/11/24/%23ubuntu-devel.html#t14:35 I have approximately 300 USB touch panels. These are from two different batches, but all report the same USB ID 0c45:8419. The manufacturer told me they had changed the firmware without changing the USB ID/version because they did not consider the change important. Both batches work correctly on Ubuntu 10.04, but only the first batch works on 14.04. The remaining batch does not so this is a regression. After plugging in, both batches appear equivalently under: /dev/input/eventNN and for both 'evtest' reports: Input device ID: bus 0x3 vendor 0xc45 product 0x8419 version 0x100 Input device name: "SONiX USB Device" … Presumably something is occuring that causes a version version of 'libev' to handle one batch differently. Attached is the output of running: $ sudo lsusb - -c -d 0c45:8419 > ….txt for one device from each of the two batches, which confirms that they appear identically. I have tested 250/250 (working) from the first batch, and 10/50 (not-working) from the second batch. The only way to tell the batches apart is by the length of the USB - cable, which is NNN centimetres LONGER/SHORTER on the working batch. + cable, the first (working) batch have USB cables that are 15-20 + centimetres long, and the second (non-working) batch have USB cables + that are ~1 metre long. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519393 Title: New revision of 0c45:8419 Microdia USB Touchscreen not working under 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evtest/+bug/1519393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519393] Re: New revision of 0c45:8419 Microdia/Wivitouch USB Infrared Touchscreen no longer working under 14.04
** Summary changed: - New revision of 0c45:8419 Microdia USB Touchscreen not working under 14.04 + New revision of 0c45:8419 Microdia/Wivitouch USB Infrared Touchscreen no longer working under 14.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519393 Title: New revision of 0c45:8419 Microdia/Wivitouch USB Infrared Touchscreen no longer working under 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evtest/+bug/1519393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519393] Re: New revision of 0c45:8419 Microdia USB Touchscreen not working under 14.04
** Attachment removed: "hidreplay-not-working .txt" https://bugs.launchpad.net/ubuntu/+source/evtest/+bug/1519393/+attachment/4524728/+files/hidreplay-not-working%20.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519393 Title: New revision of 0c45:8419 Microdia USB Touchscreen not working under 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evtest/+bug/1519393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519393] Re: New revision of 0c45:8419 Microdia USB Touchscreen not working under 14.04
** Description changed: Filing here per request at: http://irclogs.ubuntu.com/2015/11/24/%23ubuntu-devel.html#t14:35 - I have approximately fifty USB touch panels. These are from two - different batches, but all report the same USB ID 0c45:8419. The - manufacturer told me they had changed the firmware without changing the - USB ID/version because they did not consider the change important. Both - batches work correctly on Ubuntu 10.04, but only one batch works on - 14.04. As such, this is a regression. + I have approximately 300 USB touch panels. These are from two different + batches, but all report the same USB ID 0c45:8419. The manufacturer + told me they had changed the firmware without changing the USB + ID/version because they did not consider the change important. Both + batches work correctly on Ubuntu 10.04, but only the first batch works + on 14.04. The remaining batch does not so this is a regression. - After plugging in, both batches appear equivalently as: + After plugging in, both batches appear equivalently under: /dev/input/eventNN and for both 'evtest' reports: Input device ID: bus 0x3 vendor 0xc45 product 0x8419 version 0x100 Input device name: "SONiX USB Device" … Presumably something is occuring that causes a version version of 'libev' to handle one batch differently. Attached is the output of running: $ sudo lsusb - -c -d 0c45:8419 > ….txt for one device from each of the two batches, which confirms that they - appear identically. + appear identically. I have tested 250/250 (working) from the first + batch, and 10/50 (not-working) from the second batch. + + The only way to tell the batches apart is by the length of the USB + cable, which is NNN centimetres LONGER/SHORTER on the working batch. ** Changed in: evtest (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519393 Title: New revision of 0c45:8419 Microdia USB Touchscreen not working under 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evtest/+bug/1519393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519393] Re: New revision of 0c45:8419 Microdia USB Touchscreen not working under 14.04
Cesar, there is only one copy of the output of "sudo lsusb - -d 0c45:8419", please can you run if for *both* the old and new firmware- revision devices, so that it's possible to compare and see if there is a way to tell them apart. Please can you include the information from the manufacturer that confirms that they changed the firmware, without changing the USB ID. ** Summary changed: - Touchscreen not working + New revision of 0c45:8419 Microdia USB Touchscreen not working under 14.04 ** Changed in: evtest (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519393 Title: New revision of 0c45:8419 Microdia USB Touchscreen not working under 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evtest/+bug/1519393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519393] Re: New revision of 0c45:8419 Microdia USB Touchscreen not working under 14.04
(Extracted from tarball and re-attached). ** Attachment added: "lsusb--0c45:8419-not-working.txt" https://bugs.launchpad.net/ubuntu/+source/evtest/+bug/1519393/+attachment/4524711/+files/lsusb--0c45%3A8419-not-working.txt ** Description changed: Filing here per request at: - http://irclogs.ubuntu.com/2015/11/24/%23ubuntu-devel.html#t14:35 + http://irclogs.ubuntu.com/2015/11/24/%23ubuntu-devel.html#t14:35 I have approximately fifty USB touch panels. These are from two different batches, but all report the same USB ID 0c45:8419. The manufacturer told me they had changed the firmware without changing the USB ID/version because they did not consider the change important. Both batches work correctly on Ubuntu 10.04, but only one batch works on 14.04. As such, this is a regression. After plugging in, both batches appear equivalently as: - /dev/input/eventNN + /dev/input/eventNN and for both 'evtest' reports: - Input device ID: bus 0x3 vendor 0xc45 product 0x8419 version 0x100 - Input device name: "SONiX USB Device" - … + Input device ID: bus 0x3 vendor 0xc45 product 0x8419 version 0x100 + Input device name: "SONiX USB Device" + … + Presumably something is occuring that causes a version version of + 'libev' to handle one batch differently. Attached is the output of + running: - Presumably something is occuring that causes a version version of 'libev' to handle one batch differently. + $ sudo lsusb - -c -d 0c45:8419 > ….txt + + for one device from each of the two batches. ** Description changed: Filing here per request at: http://irclogs.ubuntu.com/2015/11/24/%23ubuntu-devel.html#t14:35 I have approximately fifty USB touch panels. These are from two different batches, but all report the same USB ID 0c45:8419. The manufacturer told me they had changed the firmware without changing the USB ID/version because they did not consider the change important. Both batches work correctly on Ubuntu 10.04, but only one batch works on 14.04. As such, this is a regression. After plugging in, both batches appear equivalently as: /dev/input/eventNN and for both 'evtest' reports: Input device ID: bus 0x3 vendor 0xc45 product 0x8419 version 0x100 Input device name: "SONiX USB Device" … Presumably something is occuring that causes a version version of 'libev' to handle one batch differently. Attached is the output of running: - $ sudo lsusb - -c -d 0c45:8419 > ….txt + $ sudo lsusb - -c -d 0c45:8419 > ….txt - for one device from each of the two batches. + for one device from each of the two batches, which confirms that they + appear identically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1519393 Title: New revision of 0c45:8419 Microdia USB Touchscreen not working under 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evtest/+bug/1519393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1519393] Re: New revision of 0c45:8419 Microdia USB Touchscreen not working under 14.04
(Extracted from tarball and re-attached). ** Description changed: - This new device does not work. + Filing here per request at: - EventTest of not working one - $ sudo evtest - No device specified, trying to scan all of /dev/input/event* - Available devices: - /dev/input/event0: Power Button - /dev/input/event1: Sleep Button - /dev/input/event2: Power Button - /dev/input/event3: Video Bus - /dev/input/event4: HDA Intel PCH HDMI/DP,pcm=3 - /dev/input/event5: HDA Intel PCH Front Headphone - /dev/input/event6: HDA Intel PCH Line Out - /dev/input/event7: HDA Intel PCH Line - /dev/input/event8: HDA Intel PCH Rear Mic - /dev/input/event9: HDA Intel PCH Front Mic - /dev/input/event10: SONiX USB Device - /dev/input/event11: SONiX USB Device - Select the device event number [0-11]: 10 - Input driver version is 1.0.1 - Input device ID: bus 0x3 vendor 0xc45 product 0x8419 version 0x100 - Input device name: "SONiX USB Device" - Supported events: - Event type 0 (EV_SYN) - Event type 1 (EV_KEY) - Event code 330 (BTN_TOUCH) - Event type 3 (EV_ABS) - Event code 0 (ABS_X) - Value 0 - Min0 - Max 4064 - Event code 1 (ABS_Y) - Value 0 - Min0 - Max 4064 - Event code 47 (ABS_MT_SLOT) - Value 0 - Min0 - Max7 - Event code 53 (ABS_MT_POSITION_X) - Value 0 - Min0 - Max 4064 - Event code 54 (ABS_MT_POSITION_Y) - Value 0 - Min0 - Max 4064 - Event code 57 (ABS_MT_TRACKING_ID) - Value 0 - Min0 - Max65535 - Properties: - Property type 1 (INPUT_PROP_DIRECT) - Testing ... (interrupt to exit) + http://irclogs.ubuntu.com/2015/11/24/%23ubuntu-devel.html#t14:35 - $sudo evtest - No device specified, trying to scan all of /dev/input/event* - Available devices: - /dev/input/event0: Power Button - /dev/input/event1: Sleep Button - /dev/input/event2: Power Button - /dev/input/event3: Video Bus - /dev/input/event4: HDA Intel PCH HDMI/DP,pcm=3 - /dev/input/event5: HDA Intel PCH Front Headphone - /dev/input/event6: HDA Intel PCH Line Out - /dev/input/event7: HDA Intel PCH Line - /dev/input/event8: HDA Intel PCH Rear Mic - /dev/input/event9: HDA Intel PCH Front Mic - /dev/input/event10: SONiX USB Device - /dev/input/event11: SONiX USB Device - Select the device event number [0-11]: 11 - Input driver version is 1.0.1 - Input device ID: bus 0x3 vendor 0xc45 product 0x8419 version 0x100 - Input device name: "SONiX USB Device" - Supported events: - Event type 0 (EV_SYN) - Event type 1 (EV_KEY) - Event code 330 (BTN_TOUCH) - Event type 3 (EV_ABS) - Event code 0 (ABS_X) - Value 3488 - Min0 - Max 4064 - Event code 1 (ABS_Y) - Value 2358 - Min0 - Max 4064 - Event code 47 (ABS_MT_SLOT) - Value 0 - Min0 - Max7 - Event code 53 (ABS_MT_POSITION_X) - Value 0 - Min0 - Max 4064 - Event code 54 (ABS_MT_POSITION_Y) - Value 0 - Min0 - Max 4064 - Event code 57 (ABS_MT_TRACKING_ID) - Bus 002 Device 008: ID 0c45:8419 Microdia - Value 0 - Min0 - Max65535 - Properties: - Property type 1 (INPUT_PROP_DIRECT) - Testing ... (interrupt to exit) - Event: time 1448377382.938029, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), value 5 - Event: time 1448377382.938029, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 3675 - Event: time 1448377382.938029, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 2396 - Event: time 1448377382.938029, type 1 (EV_KEY), code 330 (BTN_TOUCH), value 1 - Event: time 1448377382.938029, type 3 (EV_ABS), code 0 (ABS_X), value 3675 - Event: time 1448377382.938029, type 3 (EV_ABS), code 1 (ABS_Y), value 2396 - Event: time 1448377382.938029, -- SYN_REPORT - Event: time 1448377382.961973, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 3685 - Event: time 1448377382.961973, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 2366 - Event: time 1448377382.961973, type 3 (EV_ABS), code 0 (ABS_X), value 3685 - Event: time 1448377382.961973, type 3 (EV_ABS), code 1 (ABS_Y), value 2366 - Event: time 1448377382.961973, -- SYN_REPORT - Event: time 1448377382.985973, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), value 3689 - Event: time 1448377382.985973, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), value 2349 - Event: time 1448377382.985973, type 3 (EV_ABS), code 0 (ABS_X), value 3689 - Event: time 1448377382.985973, type 3 (EV_ABS), code 1 (ABS_Y), value 2349 - Event: time 1448377382.985973, -- SYN_REPORT - Event: time 1448377383.050025, type 3 (EV_ABS), code
[Bug 1158010] Re: Shutdown dialog asks a yes/no question but doesn't offer a binary choice
Will: Ideally, please consider getting MPT's input on this prior to picking one, he has a good knack for finding clear solutions in cases like this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158010 Title: Shutdown dialog asks a yes/no question but doesn't offer a binary choice To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1158010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 683294] Re: do not hardcode x86 hw breakpoint instruction
Woo! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/683294 Title: do not hardcode x86 hw breakpoint instruction To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/683294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449271] Re: znc-dev 1.6 will not compile modules which need libicu functions.
** Description changed: - This is an issue that I have confirmed in ZNC 1.6. + ZNC is an IRC proxy. This is an issue that I have confirmed in ZNC 1.6. When a module is being compiled by znc-buildmod as part of znc-dev, and relies on unicode support or any functions provided by the icu source package (and libicu-dev), the modules will fail to build since the `libicu-dev` package and corresponding libraries are not present. To fix this, libicu-dev needs to be listed as a build-dep for znc-dev. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449271 Title: znc-dev 1.6 will not compile modules which need libicu functions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/znc/+bug/1449271/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1379960] Re: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime)
Simon: excellent work. I have a particular fondness for reading the write-ups on this time of bug. It reminds me a little of the infamous Doesn't print on Tuesdays (bug #248619). Once again, kudos to gradually narrowing down how to replicate it, then finding it and finally offering the patch. ** Changed in: nux Status: New = Confirmed ** Package changed: unity (Ubuntu) = nux (Ubuntu) ** Changed in: nux (Ubuntu) Status: New = Confirmed ** Changed in: nux (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1379960 Title: Menu interaction in fully maximised window causes the next click on the title bar to restore the window (after 2^31ms of uptime) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1379960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455766] Re: package nginx-core 1.6.2-5ubuntu3 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug
*** This bug is a duplicate of bug 1447294 *** https://bugs.launchpad.net/bugs/1447294 ** This bug has been marked a duplicate of bug 1447294 package nginx-full 1.6.2-5ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1455766 Title: package nginx-core 1.6.2-5ubuntu3 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1455766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1449903] Re: package nginx-core 1.6.2-5ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1447294 *** https://bugs.launchpad.net/bugs/1447294 ** This bug has been marked a duplicate of bug 1447294 package nginx-full 1.6.2-5ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1449903 Title: package nginx-core 1.6.2-5ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1449903/+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 1449903] Re: package nginx-core 1.6.2-5ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1447294 *** https://bugs.launchpad.net/bugs/1447294 ** This bug has been marked a duplicate of bug 1447294 package nginx-full 1.6.2-5ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449903 Title: package nginx-core 1.6.2-5ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1449903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1455766] Re: package nginx-core 1.6.2-5ubuntu3 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug
*** This bug is a duplicate of bug 1447294 *** https://bugs.launchpad.net/bugs/1447294 ** This bug has been marked a duplicate of bug 1447294 package nginx-full 1.6.2-5ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1455766 Title: package nginx-core 1.6.2-5ubuntu3 failed to install/upgrade: subproces post-installation script geïnstalleerd gaf een foutwaarde 1 terug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1455766/+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 863358] Re: [pkg] Can't easily use Ubuntu without using Ubuntu Mono
As Ubuntu (proportional) and Ubuntu Mono have different family names
it would probably make sense to split the binary packages produced into
two .debs built at the same time—this would allow installing one or the
other. Doing this as a one-off would be painful, but it would be
relatively quick (5–10 minutes to actually change
./debian/{control,*.install} and then an hour or two testing upgrade
testing combinations) to split these at the point of doing the next
release.
It makes sense to do this at the same time as bug #851457, as the rename
to the New Debian Font Standard packaging names requires the same
operations, and this would turn two rounds into a single round.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/863358
Title:
[pkg] Can't easily use Ubuntu without using Ubuntu Mono
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-font-family/+bug/863358/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 851084] Re: [pkg] does not show up in list returned by xfontsel, don't know 14-part font name
This likely needs a day or two of debugging depending. For fixing: once it's possible to rebuild the font, this is then likely to be relatively easy to patch; either in the source, or binary. And then an hour or so to confirm the fix works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/851084 Title: [pkg] does not show up in list returned by xfontsel, don't know 14-part font name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/851084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 783220] Re: [needs-packaging] Missing packages for mbm-gpsd and mbm-gps-control
Just a general observation on timings: when I last used this it was for OpenStreetMap collection, where 1Hz is the generally required/desired rate for track collection. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/783220 Title: [needs-packaging] Missing packages for mbm-gpsd and mbm-gps-control To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/783220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1430104] Re: Uses obsolete package naming
*** This bug is a duplicate of bug 851457 *** https://bugs.launchpad.net/bugs/851457 (Hasn't been updated, because there hasn't been a upstream realise to fix it in). ** This bug has been marked a duplicate of bug 851457 [pkg] package should be renamed according to new Debian Fonts Policy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1430104 Title: Uses obsolete package naming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1430104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 934038] Re: [nc] FFe: Upload $newer upstream version
All in good time hopefully! :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/934038 Title: [nc] FFe: Upload $newer upstream version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/934038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403293] Re: Unity Dash can't understand logout, reboot, or shutdown
Install attached to: ~/.local/share/applications/logout.desktop and a Logout icon will appear in Unity when typing logout. ** Attachment added: logout.desktop https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4284166/+files/logout.desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1403293 Title: Unity Dash can't understand logout, reboot, or shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1403293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403293] Re: Unity Dash can't understand logout, reboot, or shutdown
Install attached to: ~/.local/share/applications/shutdown.desktop and a Shutdown icon will appear in Unity when typing shutdown. ** Attachment added: shutdown.desktop https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4284167/+files/shutdown.desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1403293 Title: Unity Dash can't understand logout, reboot, or shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1403293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403293] Re: Unity Dash can't understand logout, reboot, or shutdown
Lonnie: being familiar with the Design team (having worked in it…), my suspicion is that this class of feature improvement often gets bogged down for (very) long periods of time. Therefore a method that can be deployed (or at least prototyped) immediately using existing external mechanisms is far more likely to succeed and get deployed. The example .desktop might not be the ultimate solution, but being text files that are immediately deployable without needing system-level privileges I would hope are something yourself, or anyone else, could use for developing a fuller prototype and proposal. ** Description changed: - In their efforts to make the Unity Dash the goto place for everything - you want to do, the developers have over looked 3 fundamental tasks - that a user might intuitively try to achieve with the unity dash: + This bug proposes the additional surfacing of power-management and + session actions directly within the Dash: - Reboot (restart is another good alias for this) - Shutdown (other intuitive aliases: shut down, turn off) - logout (aliases: log out, log off and logoff) - - Suspend/hibernate - - Lock - - Switch User + - Suspend/hibernate + - Lock + - Switch User + Currently these user-initiates actions are presented via the Devices + (cog/gear-icon-menu), and can be accessed via the keyboard using either: - I realize that the gear-icon-menu is the intended method for achieving such tasks, but consider this: + 1. [Alt]+[F10] [Left] [Up/Down] [Enter] + 2. [Alt] Shutdown/Log out [Up/Down] [Enter] + 3. [Ctrl]+[Alt]+[Del] [Enter] (Log off only) + 4. [Ctrl]+[Alt]+[t] sudo reboot [Enter] - That menu is not intuitively accessible via the keyboard. Try to access it without your mouse! It might be possible, but if so, it is not intuitive. I realized this today, when I encountered a bug where my mouse-cursor did not appear after logging in to the Unity Desktop: - https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403287 + (Note that Restart/Reboot can be access directly via these methods). - Additionally, ctrl-alt-delete doesn't provide a reboot option: - https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403289 + These methods are less likely to be found by the user than surfacing these actions additionally within the Dash. This would help in cases were a mouse/point is no longer available, such as mouse-cursor did not appear after logging in to the Unity Desktop + https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403287 - There are clearly circumstances where it would be very nice to reboot or - shutdown your computer via the dash. As a matter of fact, I think it - would be my preferred method of achieving these task if it were - available. Instead of mousing to the gear menu (and clicking a menu - option), I would much rather hit the super key and type reboot or - restart. + This would also assist with ctrl-alt-delete doesn't provide a reboot option + https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403289 - Granted, I could achieve this via Unity Alt-key menu, or by hitting - ctrl-alt-T, but you have to type sudo reboot (and enter your dang - password) to achieve this. I'd rather go the gear-icon-method than be - required to type my password! + It is proposed by surfacing these options in the Unity Dash, that + finding the actions would be more intuitive, and would make the Dash + feel more complete as the defacto first-point-of-call for user initiated + actions. - Therefore, this unity-dash method I'm proposing would be a nice - compromise. And, from an intuitive perspective, its simply an oversight - (everyone has ignored) that should have been there all along, - respectfully. - - ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 - ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 - Uname: Linux 3.13.0-43-generic x86_64 - NonfreeKernelModules: nvidia - .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' - .proc.driver.nvidia.registry: Binary: - .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.113 Mon Dec 1 21:08:13 PST 2014 - GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) - .tmp.unity.support.test.0: - - ApportVersion: 2.14.1-0ubuntu3.6 - 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 - CurrentDesktop: Unity - Date: Tue Dec 16 21:31:36 2014 - DistUpgraded: Fresh install - DistroCodename: trusty - DistroVariant: ubuntu - GraphicsCard: - NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) - Subsystem: Hewlett-Packard Company Device [103c:7001] - InstallationDate: Installed on 2014-11-23 (23 days ago) - InstallationMedia: Ubuntu
[Bug 1403293] Re: Unity Dash can't understand logout, reboot, or shutdown
** Attachment removed: xserver.devices.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282487/+files/xserver.devices.txt ** Attachment removed: xdpyinfo.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282486/+files/xdpyinfo.txt ** Attachment removed: nvidia-settings.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282485/+files/nvidia-settings.txt ** Attachment removed: Xrandr.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282484/+files/Xrandr.txt ** Attachment removed: XorgLogOld.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282483/+files/XorgLogOld.txt ** Attachment removed: XorgLog.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282482/+files/XorgLog.txt ** Attachment removed: UdevLog.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282480/+files/UdevLog.txt ** Attachment removed: UdevDb.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282479/+files/UdevDb.txt ** Attachment removed: .proc.driver.nvidia.params.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282463/+files/.proc.driver.nvidia.params.txt ** Attachment removed: UnitySupportTest.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282481/+files/UnitySupportTest.txt ** Attachment removed: ProcModules.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282478/+files/ProcModules.txt ** Attachment removed: ProcInterrupts.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282477/+files/ProcInterrupts.txt ** Attachment removed: ProcEnviron.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282476/+files/ProcEnviron.txt ** Attachment removed: ProcCpuinfo.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282475/+files/ProcCpuinfo.txt ** Attachment removed: NvidiaBugReportLog.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282474/+files/NvidiaBugReportLog.txt ** Attachment removed: MonitorsUser.xml.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282473/+files/MonitorsUser.xml.txt ** Attachment removed: Lsusb.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282472/+files/Lsusb.txt ** Attachment removed: Lspci.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282471/+files/Lspci.txt ** Attachment removed: GconfCompiz.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282470/+files/GconfCompiz.txt ** Attachment removed: DpkgLog.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282469/+files/DpkgLog.txt ** Attachment removed: DkmsStatus.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282468/+files/DkmsStatus.txt ** Attachment removed: Dependencies.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282467/+files/Dependencies.txt ** Attachment removed: CurrentDmesg.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282466/+files/CurrentDmesg.txt ** Attachment removed: BootLog.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282465/+files/BootLog.txt ** Attachment removed: BootDmesg.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1403293/+attachment/4282464/+files/BootDmesg.txt ** Description changed: This bug proposes the additional surfacing of power-management and session actions directly within the Dash: - Reboot (restart is another good alias for this) - Shutdown (other intuitive aliases: shut down, turn off) - logout (aliases: log out, log off and logoff) - Suspend/hibernate - Lock - Switch User - Currently these user-initiates actions are presented via the Devices + Currently these user-initiated actions are presented via the Devices (cog/gear-icon-menu), and can be accessed via the keyboard using either: 1. [Alt]+[F10] [Left] [Up/Down] [Enter] 2. [Alt] Shutdown/Log out [Up/Down] [Enter] 3. [Ctrl]+[Alt]+[Del] [Enter] (Log off only) 4. [Ctrl]+[Alt]+[t] sudo reboot [Enter] - (Note that Restart/Reboot can be access directly via these methods). + (Note that Restart/Reboot can not be accessed directly via 1-3). - These methods are less likely to be found by the user than surfacing these actions additionally within the Dash. This would help in cases were a mouse/point is no longer available, such as mouse-cursor did not appear after logging in to the Unity Desktop + These methods are less likely to be found by the user than surfacing these actions additionally within the Dash. This
[Bug 1403293] Re: Unity Dash can't understand logout, reboot, or shutdown
It should be possible to solve this by providing a '.desktop' file containing entries for 'shutdown', 'logout', and 'reboot/restart'; and then it's not a Unity dash issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1403293 Title: Unity Dash can't understand logout, reboot, or shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1403293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 864323] Re: Category fonts in application lens is empty thus obsolete
Is the category empty for a reason, or is the filtering just broken? (If so that could be fixed instead of removal). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/864323 Title: Category fonts in application lens is empty thus obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/864323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974480] Re: Notification area whitelist is obsolete
Anton: I'm interested in understanding the situation a little better: 1. Internal applications originally targeting eg. GNOME 2, and you're now needing to run these under Unity. 2. Bought-in (external non-IBM) applications originally targeting eg. GNOME 2, and you're now needing to run these under Unity. 3. Something else? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974480 Title: Notification area whitelist is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 784549] Re: Mono: Style: Cyrillic Ghe Г has incorrect bottom serif and looks strange
Clockwork: The glyph has been replaced in 0.910-prerelease (see above). 0.910 currently has other regressions that make it hard to release in its current form. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/784549 Title: Mono: Style: Cyrillic Ghe Г has incorrect bottom serif and looks strange To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/784549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 784549] Re: Mono: Style: Cyrillic Ghe Г has incorrect bottom serif and looks strange
Hello Alex, Г has been fixed in the 0.910-prerelease Ubuntu Mono received from Dalton Maag. This PDF should shows the Russian, Ukrainian and some other Balkan Cyrillic glyphs as they are in the 0.910-prerelease mono. The 0.910-prelease has a number of other fixes (this is a good thing), but also some regressions introduced against the 0.89 currently in circulation (not so ideal). The regressions include glyph changes to earlier versions that had already been fixed in 0.89 and because the baseline spacing has been increased, causing document reflow. The problem exists on how to work from the binary TTFs, and perform a three-way merge, keeping the manual hinting, backing out the regressions, but keeping bug fixes and improvements. Help, guidance and suggestions would be appreciated; we have the source, but the manual hinting and VOLT engineering is applied afterwards! ** Attachment added: ubuntu-mono-0.910prerelease-cyrillic-sampler-lp784549.pdf https://bugs.launchpad.net/ubuntu-font-family/+bug/784549/+attachment/4116680/+files/ubuntu-mono-0.910prerelease-cyrillic-sampler-lp784549.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/784549 Title: Mono: Style: Cyrillic Ghe Г has incorrect bottom serif and looks strange To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/784549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314616] Re: bitcoin to be maintained upstream in PPA: Replace distro archive bitcoin bitcoin with an empty dummy package
** Summary changed: - Replace the package bitcoin with an empty dummy package + bitcoin to be maintained upstream in PPA: Replace distro archive bitcoin bitcoin with an empty dummy package ** Description changed: + The Bitcoin utilities are a set of virtual-currency tools. Going + forward the upstream maintainers have expressed a wish to maintain + 'bitcoin' in a PPA; superseding the version in the main archives. The + 'bitcoin' package has already been removed from 'trusty' and blacklisted + from synching going forward. This bug report covers earlier versions of + Ubuntu, where it is intended to replace the in-archive versions with a + dummy package directing users towards the PPA-maintained copy. + See the mailing list discussions at https://lists.ubuntu.com/archives /ubuntu-motu/2013-December/thread.html and https://lists.ubuntu.com/archives/ubuntu-motu/2014-April/thread.html. In short: old versions of Bitcoin Core (as it is now known) are broken, not up to date on bug fixes, etc. http://packages.ubuntu.com/search?keywords=bitcoinsearchon=namessuite=allsection=all shows that these old versions of the package are shipped in precise, raring, and saucy. In the past, I'm pretty sure it's also shown version 0.6.something in quantal, but that appears to have disappeared from the search. My understanding from the ML discussions earlier is that it's impossible to remove a package from the package lists, but it could be replaced with an SRU by a dummy package that explains to the user why it's gone and prompts them to download the software either from the PPA (ppa:bitcoin/bitcoin) or the release binaries from bitcoin.org. This is what I'd like to request be done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314616 Title: bitcoin to be maintained upstream in PPA: Replace distro archive bitcoin bitcoin with an empty dummy package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bitcoin/+bug/1314616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 651064] Re: Missing pixmap for Australia/Eucla timezone
Hadess: I had been looking that this; and my presumption is that each layer shown/hidden/exported from Inkscape one at a time. But it's definitely something that I'll make scripted so it's easy to re-export the whole suite at $preferred_bitmap_size. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/651064 Title: Missing pixmap for Australia/Eucla timezone To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/651064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 651064] Re: Missing pixmap for Australia/Eucla timezone
Now split out into: https://launchpad.net/timezonemap ** Also affects: ubiquity Importance: Undecided Status: New ** Project changed: ubiquity = timezonemap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/651064 Title: Missing pixmap for Australia/Eucla timezone To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/651064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248351] Re: Common Dutch US international not available
** Summary changed: - English US international not behaving as expected. + Common Dutch US international not available -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248351 Title: Common Dutch US international not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1248351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1248351] Re: Common Dutch US international not available
** Description changed: - Problem: - Dead keycombinations not working as expected, for example I'm becomes Iḿ. - Adding a spreadsheet with every dead keycombination that doesn't work as expected (expected output included). + In System Settings-Keyboard Layouts-Add the following Dutch layouts + are available: - Solution: - Add a Dutch (US international with dead keys) layout. + Dutch + Dutch (Macintosh) + Dutch (standard) + Dutch (Sun dead keys) + + None of these are the common layout that Dutch users coming from MS + Windows may have used. The Dutch (Macintosh) layout is close, but + differs in the dead-keys configuration. Over the years, other users + have observed the same issue: + + Add a Dutch (US international with dead keys) layout. + + Ideally a Dutch (US international with dead keys) layout should be + added to 'xkb-data' so that users can view it. Note that the available + layouts available on the console differ from those available under the + GUI. + + The dead keycombinations not working as expected are: + + 1. I'm becomes Iḿ. + + (other combinations to follow). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1248351 Title: Common Dutch US international not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1248351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205791] Re: Dell Vostro V131: special keys not working
** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205791 Title: Dell Vostro V131: special keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205791] Re: Dell Vostro V131: special keys not working
** Tags removed: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205791 Title: Dell Vostro V131: special keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205791] Re: Dell Vostro V131: special keys not working
Whoopie: please can you attach a copy of 'lspnp'. ** Description changed: - Hi, + Bug filed, following conversation on IRC at: - I own a Dell Vostro V131. This model has 3 special hotkeys (quick launch keys, see http://www.notebookcheck.net/fileadmin/_migrated/pics/v131tastatur_01.jpg). - The keys are: - 1. Windows mobility center (this hotkey generates Mod+X) - 2. Dell support center - 3. Dell instant launch manager + http://irclogs.ubuntu.com/2013/07/28/%23ubuntu-devel.html#t07:45 + + I own a Dell Vostro V131. This model has 3 special hotkeys (quick launch + keys: + + http://www.notebookcheck.net/fileadmin/_migrated/pics/v131tastatur_01.jpg + + There are documented in page 1 of the manual: + + ftp://ftp.dell.com/Manuals/all- + products/esuprt_laptop/esuprt_vostro_notebook/vostro-v131_Setup + %20Guide_en-us.pdf + + as being: + + 1. Windows mobility center (this hotkey generates [Mod]+[x]) + 2. Dell support center + 3. Dell instant launch manager + + This was previous raised at: + + http://www.mail-archive.com/platform-driver-x86@vger.kernel.org/msg03124.html + http://www.mail-archive.com/platform-driver-x86@vger.kernel.org/msg0.html The Dell support center key generates keycode 0xEE, but misses release event. I got it working with an udev keyboard force release quirk, see - attached patch. + attached patch in the '' email. - The Dell instant launch manager key doesn't generate anything, neither - through dell-wmi nor i8042. It's the rightmost button in the right upper - corner of the keyboard. + However, the Dell instant launch manager key doesn't generate + anything, neither through dell-wmi nor i8042. It's the rightmost button + in the right upper corner of the keyboard. The ACPI interrupt-count + appears to increment, as seen with: + + http://www.mail-archive.com/platform-driver-x86@vger.kernel.org/msg03126.html + watch -n 0,1 cat /proc/interrupts -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205791 Title: Dell Vostro V131: special keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205791] Re: Dell Vostro V131: special keys not working
Page 12 of: http://odm.ubuntu.com/uhs/2011/Enabling%20Hotkey%20Features%20on%20Ubuntu.pdf gives this as the Dell WMI GUID: 9DBB5994-A997-11DA-B012-B622A1EF5492 dell_wmi Whoopie: are you seeing unhandled WMI event at the same time as the key is pressed? If this is not obviously the case it worth poking Seth Forshee (Canonical) and Rezwanul Kabir (Dell) to find out if a knock-code or something else is required. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205791 Title: Dell Vostro V131: special keys not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 738302] Re: My scanner [Canon, Inc. CanoScan 3200F] works with windows xp but doesn't with ubuntu
$ lsb_release -d Description:Ubuntu 12.04.2 LTS $ lusb | grep Canon Bus 002 Device 010: ID 04a9:2216 Canon, Inc. CanoScan 3200F $ sane-find-scanner found USB scanner (vendor=0x04a9, product=0x2216, chip=GL841?) at libusb:002:010 found USB scanner (vendor=0x147e, product=0x2016) at libusb:001:003 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. $ scanimage --list-devices No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/738302 Title: My scanner [Canon, Inc. CanoScan 3200F] works with windows xp but doesn't with ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/738302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769874] Re: Naming restrictions in UFL considered non-free by Debian
Ejectmail, thank you for looking into it. Remember that the interim UFL
has drawn up as a first take, with the hope to refine it, so input is
appreciated, because out of it we can get a better libre font licence
than the choices that were available at the time.
Obviously one must start somewhere. Ine must ensure that one always has
the source code, the freedom to modify it, the freedom to give it to
other people, and the freedom to sell it. The interim UFL has, as a
minimum, all of these. I'm sure wording could be improved but it has a
good foundation (note: the propagation wording is straight out of the
GPLv3, various other sections come from SIL's OFL).
Onto trademarks, Trademarks, are about the point of use; and whether a
consumer would be confused. It *is* possible to say (quite factually)
Iceweasel is based on Firefox, or Iceweasel is Firefox with branding
removed. What one cannot do is to say Iceweasel is {insert huge big
Firefox logo}. Indeed, free-software licences demand that attribution
is made available and that the authorship is not misrepresented.
In the interim UFL text, one could potentially remove the (explicit)
trademark sentence, and leave it simply (implicit). The net-effect
would be the same (that you can't misrepresent to consumers that you are
somebody, or something else).
The intention was to get existing type foundries working with a libre
licence. I think the intention was to make it abundantly that people
wouldn't be able to pick up MonoType FooBar Bold and sell it as genuine
MonoType(tm) when they didn't have a trademark agreement to do so.
The bigger picture is what is important here. Making a libre font
licence that *real type design companies* might actually be comfortable
with using on a large-scale, and which caters to their concerns in terms
of metrics-stability and not having a product passed off. For code, the
industry with the GPLv2 and GPLv3. For fonts, it's not yet clear, and
the hope was to try and solve that.
(nb. I know that the word Ubuntu here can be emotive, you're welcome
to replace it with another word if it makes the discussion easier.
Having Ubuntu there in the interim licence ensures that it won't be
used elsewhere until it has been debugged. And that's where I would
appreciate your assistance).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/769874
Title:
Naming restrictions in UFL considered non-free by Debian
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-font-family/+bug/769874/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1161840] Re: DOES NOT GO TO ELEVEN
NOPE, VOLUME KEYS HAVE ALWAYS BEEN ALWAYS RELATIVE (CAPPED AT) 100% WHEN GOING UP. ** Package changed: unity (Ubuntu) = gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1161840 Title: DOES NOT GO TO ELEVEN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1161840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 650498] Re: Expansion: 'ẞ' LATIN CAPITAL LETTER SHARP S (U+1E9E)
Adolfo: please could you attach the curve files that you were working with to this bug report so they don't get lost. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/650498 Title: Expansion: 'ẞ' LATIN CAPITAL LETTER SHARP S (U+1E9E) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/650498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1139358] Re: U+2E2A through U+2E2C glyphs swapped
What font name is display when right-clicking on these glyphs in the Character Map (this shows which font they are really coming from). If I select Ubuntu and then right-click on these glyphs it shows me that they are originating from FreeSans. Is this what you see too? ** Changed in: ubuntu-font-family-sources (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1139358 Title: U+2E2A through U+2E2C glyphs swapped To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1139358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111808] Re: Unity Legal notice
Nicolò: I'd really like not to have a EULA style box. Users have negative feelings towards whack-a-mole popups and EULA windows between between them and the interface. User tend to dismiss them anyway but remember the annoyance. A few years ago Mozilla tried something very similar with Firefox by adding a EULA; it was removed afterwards and replaced with tiny little bar at the top of a first-use Firefox instance that says Know your Freedoms. Anything more than this is clunky, and the negative vibes will outweight any positive comfort benefit that can be achieved from showing it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/808 Title: Unity Legal notice To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1111808] Re: Unity Legal notice
Nicolò: OTOH, it would increase code in Unity Dash for very little gain, and probably negative gain. Firstly it's a 90%/10% thing; the legal notice is not frequently used, but still needs to be reliable and easy to interact with when required. The current situation of using a Web browser would seem to meet that require elegantly. Second, the concept of the Dash is a search enabler, rather than a content interface; so you pop the Dash overlay, /find/ what you want, and launch to that task or content. /Doing work/ inside Unity Dash would defeat that premise, because you may not recursively pop up the Unity Dash over itself. The current setup is, I believe, more functional and consistent. For example, by opening the legal task in a web browser, the user can then be reading that legal text, discover a term they are not sure about, and then bring up the Unity Dash to locate the legal phase via the Legal Eagle(tm) Dictionary Lens from LegalLegalSons(tm). If you were performing the task within Unity Dash itself, recursion would not be possible, and the user would be at a disadvantage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/808 Title: Unity Legal notice To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974480] Re: Notification area whitelist is obsolete
Miguel/Cliff: it's a bit of a backronym, but perhaps think of it this way. We have the *buntu core (kernels, system libraries, brand, fonts, …) on top of which are built several optimised distributions (remixes): KDE: [Ku]buntu LxDE: [Lu]buntu XDE: [Xu]ubuntu Unity: [U]buntu Gnome3 Shell: [G]ubuntu There are other ones for Education, for GNOME 3 Shell, for music production, and dozens more. Each has a slightly different target; what they share is the core, the Debian packaging and the infrastructure, parts of the brand and five letters of the name. Various people (mainly via Canonical) maintain/garden the infrastructure for most of these remixes, particularly the Launchpad service, the build daemons to build all the Debian packages and the main FTP servers to distribute them. And various people then make the specific remixes *work*: those people are often individuals, small companies (such as Blue Systems); often big companies (particularly via Canonical). Now where people have their day job they are necessaryily going to be focused the dayjob since that's why they're being retained. So, there's KDE people at Blue Systems who spend their time focused on the KDE parts of Kubuntu. There's Unity people in Canonical's Design/Desktop Experience team who spend their time focused on the Unity parts of Ubuntu. Kubuntu won't run Gnome 3 Shell applications without additional libraries/infrastructure; and GNOME3 Shell won't run KDE programs without additional libraries, and even when they are run as crossovers, the level of seemless integration will be less. The same is the case Unity, Enlightenment, and everything else: the integration with be less in a differing environment. Miguel: you've particularly mentioned Unity/UbuntuPhone and Unity/UbuntuTV and it'll be good to see the apps targeted at these (it's not just you that thinks they're cool). You've also mentioned the various work applications (TrueCrypt), so the question is what are these targeting? Are they targetting Ubuntu (Unity), or Gubuntu (GNOME3 Shell), or Kubuntu (KDE4). Do they know what their customers are wanting? There's quite a bit of follow the money here; if your company is a customer of the makers of a programme (you won't be the only one) then it really focuses the attention to _state that Unity support is required_. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974480 Title: Notification area whitelist is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974480] Re: Notification area whitelist is obsolete
James: I think a lot of it is about works with Ubuntu vs. works against some APIs that were made 10 years ago, and which most/some Unices' Windows Managers have supported at some time. For stuff to work with *the Ubuntu experience* some effort will be required; this is much the same as following the HIG on Mac OSX. [*] I'm tempted to suggest that the way to go with this is to have a separate application (_not_ part of the Unity, or Ubuntu APIs) which provides a implementation of the tray manager end per: http://www.freedesktop.org/wiki/Specifications/systemtray-spec and which punts those requestes to a regular application window near a corner. Anything using the Systray API is not introspectable, it's not accessible and it's not really suitable for providing the depth of metadata necessary for the interface or for those who cannot see a grid of pixels. However, a separate implementation of the tray manager API would provide a legacy solution, and the .deb Recommends can pull in that shim when it's required so that it's only installed when such applications are pulled in. [*] The counter for this would be that both Microsoft and the Linux kernel have succeeded for twenty years with prioritising mostly-reliable handling of previous generations of APIs. A separate shim application here would provide somewhere reasonably sandboxed to let legacy apps draw into their legacy raw container windows, while making it clear that these aren't a supported solution going forward, and importantly would get that code out of the Unity menubar implementation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974480 Title: Notification area whitelist is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974480] Re: Notification area whitelist is obsolete
Chris: which (precise) applications that you use for work do not support the Unity global menu? For example, for myself, there are two applications without have global menu support: 1. JOSM (OpenStreetMap editor, Java-based owing to portability) 2. Fontforge (purely custom widget set, owing to age and other widgets sets not then supporting Unicode reliably) that said, neither of these use the menubar for status (so I think the difference would be null here). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974480 Title: Notification area whitelist is obsolete To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1109890] Re: Unicode 25D2 Circle With Lower Half Black and 25D3 swapped in most fonts
Probably the easiest is to start gnome-character-map/gcharmap; select Ubuntu, search to U+25D2 and then *right-click* on the glyph. This will then show a larger rendering of the glyph and state the _actual_ font that the glyph is coming from in the pop-up. Depending on whether it's correct or not you can go through the list of other fonts and see which ones are swapped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1109890 Title: Unicode 25D2 Circle With Lower Half Black and 25D3 swapped in most fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1109890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1109890] Re: Unicode 25D2 Circle With Lower Half Black and 25D3 swapped in most fonts
** Package changed: ubuntu-font-family-sources (Ubuntu) = ttf-dejavu (Ubuntu) ** Bug watch added: freedesktop.org Bugzilla #55197 https://bugs.freedesktop.org/show_bug.cgi?id=55197 ** Also affects: dejavu-fonts via https://bugs.freedesktop.org/show_bug.cgi?id=55197 Importance: Unknown Status: Unknown ** Summary changed: - Unicode 25D2 Circle With Lower Half Black and 25D3 swapped in most fonts + Unicode 25D2 Circle With Lower Half Black and 25D3 swapped in DejaVu ** Summary changed: - Unicode 25D2 Circle With Lower Half Black and 25D3 swapped in DejaVu + Unicode 25D2 Circle With Lower Half Black and 25D3 swapped in DejaVu Sans and DejaVu Serif -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1109890 Title: Unicode 25D2 Circle With Lower Half Black and 25D3 swapped in DejaVu Sans and DejaVu Serif To manage notifications about this bug go to: https://bugs.launchpad.net/dejavu-fonts/+bug/1109890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1109890] Re: Unicode 25D2 Circle With Lower Half Black and 25D3 swapped in most fonts
From memory we don't have these two glyphs in the Ubuntu Font Family yet; would you be able to supply a screenshot so that we can try and work out where they're being substituted from and fix them in /that/ font. ** Changed in: ubuntu-font-family-sources (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1109890 Title: Unicode 25D2 Circle With Lower Half Black and 25D3 swapped in most fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1109890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1083333] Re: Need greeter 13.04 logo asset
For anyone wondering, Xi's PNG is correct and is white-on-white; the white text is solid/opaque and the white background is transparent. The text reads ubuntu^ 13.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/108 Title: Need greeter 13.04 logo asset To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016824] Re: Ubuntu wallpapers are low quality (low resolution, JPEG artefacts, noise)
Hello Daniel; thank you for the comment. While the point about dithering may be valid different issue though; one of style/technical choices; rather than of JPEG compression. Would you be able to file it as a new, separate issue, if you'd still like to follow it up? ** Changed in: ayatana-design Status: New = Fix Released ** Changed in: ubuntu-branding Status: New = Fix Released ** Changed in: ubuntu-wallpapers (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016824 Title: Ubuntu wallpapers are low quality (low resolution, JPEG artefacts, noise) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1016824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016824] Re: Ubuntu wallpapers are low quality (low resolution, JPEG artefacts, noise)
Marking as Fixed, as the core issue of size restrictions leading to high-compression is hopefully resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016824 Title: Ubuntu wallpapers are low quality (low resolution, JPEG artefacts, noise) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1016824/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218712] Re: Backlight brightness on Lenovo R61 won't go all the way down
Hi Sam, as a work-around, try Shift+Fn+Home/End. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/218712 Title: Backlight brightness on Lenovo R61 won't go all the way down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/218712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1055766] Re: grep -R doesn't automatically search amazon
** Changed in: gnome-terminal (Ubuntu) Status: Incomplete = Invalid ** Changed in: command-not-found (Ubuntu) Status: Incomplete = Invalid ** Changed in: ayatana-design Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1055766 Title: grep -R doesn't automatically search amazon To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1055766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1055766] Re: grep -R doesn't automatically search amazon
Stephen: It's not really ideal, but I can try shunting it around to increase the likelihood of a 60-day time out happening. I'd welcome any more-ideal solutions/suggestions if somebody can make them. I have a feeling that Launchpad used to have a null project for shunting miscellaneous items too. (If all else fails I'm happy to move it to ubuntu-branding, where it'll still be on my watchlist, but not on other people's to such a degree). ** No longer affects: command-not-found (Ubuntu) ** No longer affects: gnome-terminal (Ubuntu) ** Project changed: ayatana-design = command-not-found ** Project changed: command-not-found = command-not-found (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1055766 Title: grep -R doesn't automatically search amazon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1055766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1055766] Re: grep -R doesn't automatically search amazon
drmgiver: What would you like to see done? Could you please explain how setting it to confirmed helps? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1055766 Title: grep -R doesn't automatically search amazon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1055766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1055766] Re: grep -R doesn't automatically search amazon
Sergei: go for it! It should be possible to do something with the machine's webcam and Processing: http://processing.org/ plus some OCR. The search domain could be kept smaller by cross- referencing potential CD/Album title matches with FreeDB to look up the contents of a CD once you have the initial name match. Or perhaps initially ask the user to wave the album barcode to the computer. A 'unity-physical-bookshelf-lens' sounds a very interesting possibility with lots of opportunity for RD into how centralised search could fit with enabling the user to find information more easily. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1055766 Title: grep -R doesn't automatically search amazon To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1055766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
