[Touch-packages] [Bug 1916915] Re: Incorrect package version available on bionic pool (2.7.17-1~18.04ubuntu1.3 not availbale)
Same for Ubuntu 16.04.7: Err:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 python2.7 amd64 2.7.12-1ubuntu0~16.04.14 404 Not Found [IP: 91.189.88.142 80] Err:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libpython2.7-stdlib amd64 2.7.12-1ubuntu0~16.04.14 404 Not Found [IP: 91.189.88.142 80] Err:3 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 python2.7-minimal amd64 2.7.12-1ubuntu0~16.04.14 404 Not Found [IP: 91.189.88.142 80] Err:4 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libpython2.7-minimal amd64 2.7.12-1ubuntu0~16.04.14 404 Not Found [IP: 91.189.88.142 80] Err:5 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libpython2.7 amd64 2.7.12-1ubuntu0~16.04.14 404 Not Found [IP: 91.189.88.142 80] # apt-cache policy python2.7 python2.7: Installed: 2.7.12-1ubuntu0~16.04.13 Candidate: 2.7.12-1ubuntu0~16.04.14 Version table: 2.7.12-1ubuntu0~16.04.14 500 500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2.7.12-1ubuntu0~16.04.13 100 100 /var/lib/dpkg/status 2.7.11-7ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1916915 Title: Incorrect package version available on bionic pool (2.7.17-1~18.04ubuntu1.3 not availbale) Status in python2.7 package in Ubuntu: Confirmed Bug description: Apt tries to get the python2.7 package and some of its dependencies with version (2.7.17-1~18.04ubuntu1.3). However it returns an error with: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-minimal_2.7.17-1~18.04ubuntu1.3_amd64.deb 404 Not Found [IP: 91.189.88.152 80] The problem is present on BIONIC distro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1916915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 992194] Re: BOM symbols in ru_RU.aff affect some package installation
Still affects Ubuntu 16.04 on installation of Postgres 9.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hunspell-ru in Ubuntu. https://bugs.launchpad.net/bugs/992194 Title: BOM symbols in ru_RU.aff affect some package installation Status in hunspell-ru package in Ubuntu: Confirmed Bug description: BOM symbols (http://en.wikipedia.org/wiki/Byte_order_mark) in ru_RU.aff affect some package installation. 1) Ubuntu 12.04 amd64 release 2) hunspell-ru 20120101-1 from postgresql 9.1 installation log: Building PostgreSQL dictionaries from installed myspell/hunspell packages... en_au en_gb en_us en_za ERROR: no ecoding defined in /usr/share/hunspell/ru_RU.aff, ignoring When BOM removed from ru_RU.aff, encoding (UTF8) is recognized and installation processed without errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-ru/+bug/992194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 992194] Re: BOM symbols in ru_RU.aff affect some package installation
The files /usr/share/hunspell/ru_RU.aff and /usr/share/hunspell/ru_RU.dic also have wrong line endings: "\r\n" instead of just "\n". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hunspell-ru in Ubuntu. https://bugs.launchpad.net/bugs/992194 Title: BOM symbols in ru_RU.aff affect some package installation Status in hunspell-ru package in Ubuntu: Confirmed Bug description: BOM symbols (http://en.wikipedia.org/wiki/Byte_order_mark) in ru_RU.aff affect some package installation. 1) Ubuntu 12.04 amd64 release 2) hunspell-ru 20120101-1 from postgresql 9.1 installation log: Building PostgreSQL dictionaries from installed myspell/hunspell packages... en_au en_gb en_us en_za ERROR: no ecoding defined in /usr/share/hunspell/ru_RU.aff, ignoring When BOM removed from ru_RU.aff, encoding (UTF8) is recognized and installation processed without errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hunspell-ru/+bug/992194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1076224] Re: [P5Q-E, Analog Devices AD1989B, Other SPDIF Out, Rear] No sound at all
I have got sound problem after selecting output device at gnome sound setting. After selecting sound output profile (one of pacmd list-cards) sound appears. pacmd set-card-profile 0 output:analog-surround-51 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1076224 Title: [P5Q-E, Analog Devices AD1989B, Other SPDIF Out, Rear] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I just switched over from Windows Vista Ultimate Package and everything "sound wise" was working absolutely normal. I was wondering if I could recieve any support with this because I am new to ubuntu somewhat ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ethan 2052 F pulseaudio /dev/snd/pcmC0D1p: ethan 2052 F...m pulseaudio /dev/snd/controlC1: ethan 2052 F pulseaudio Date: Wed Nov 7 23:17:50 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2012-11-08 (0 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ethan 2052 F pulseaudio /dev/snd/pcmC0D1p: ethan 2052 F...m pulseaudio /dev/snd/controlC1: ethan 2052 F pulseaudio Symptom_Jack: Other SPDIF Out, Rear Symptom_Type: No sound at all Title: [P5Q-E, Analog Devices AD1989B, Other SPDIF Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd08/05/2008:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1076224/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1073659] Re: Long delay between print job creation and actual start of printing
That's ridiculous. After six years of neglect I no longer have the device nor the EOLed Kubuntu Precise. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1073659 Title: Long delay between print job creation and actual start of printing Status in cups package in Ubuntu: Incomplete Bug description: I'm using Epson Stylus Office B42WD with following drivers: a) Epson Stylus Office B40W - CUPS+Gutenprint v5.2.8-pre1 b) Epson WorkForce 635 - CUPS+Gutenprint v5.2.8-pre1 With both of them, when I create a print job (especially when selecting high resolution in options), I have to wait several minutes while cups web interface reports state of job as "Printing page 1, XX%". And only when this status changes to "Spooling page, XX%" does the printer grab the paper and start printing. In contrast, Windows driver starts printing immediately, which is what I'd wish to see in Linux too. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups 1.5.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic-pae 3.2.30 Uname: Linux 3.2.0-32-generic-pae i686 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu14 Architecture: i386 Date: Wed Oct 31 21:27:54 2012 InstallationMedia: Kubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120820.1) Lpstat: device for Brother_HL5250DN: socket://192.168.0.124:9100 device for EPSON_AL-C1100: ipp://192.168.0.200:631/printers/EPSON_AL-C1100 device for Epson_Stylus_Office_B42WD: dnssd://EPSONA9A0CD%20(Epson%20Stylus%20Office%20B42WD)._printer._tcp.local/ device for Epson_Stylus_Office_B42WD2: dnssd://EPSONA9A0CD%20(Epson%20Stylus%20Office%20B42WD)._printer._tcp.local/ device for Stylus-Photo-R300: usb://EPSON/Stylus%20Photo%20R300?serial=L16P10312131556310=1 MachineType: ASUSTeK Computer INC. 1015PN Papersize: A4 PpdFiles: Epson_Stylus_Office_B42WD2: Epson WorkForce 635 - CUPS+Gutenprint v5.2.8-pre1 Epson_Stylus_Office_B42WD: Epson Stylus Office B40W - CUPS+Gutenprint v5.2.8-pre1 Stylus-Photo-R300: Epson Stylus Photo R300 - CUPS+Gutenprint v5.2.8-pre1 Brother_HL5250DN: Brother HL-5250DN BR-Script3 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-32-generic-pae root=UUID=ba1c9122-070c-42be-a418-236149e42c8d ro quiet splash acpi_osi=Linux vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1015PN dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd04/18/2011:svnASUSTeKComputerINC.:pn1015PN:pvrx.x:rvnASUSTeKComputerINC.:rn1015PN:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1015PN dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. mtime.conffile..etc.cups.cupsd.conf: 2012-10-31T20:57:39.066139 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1073659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
The issue is affecting me as well, GTX 1050, ASUS laptop. None of the resolution tactics proposed so far helped in loading the drivers properly. The only way to load the system is to add nomodeset and acpi=off in the grub menu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 803858] Re: No language chooser on login screen in LightDM
So apparently this is fixed in GTK greeter. But what about KDE greeter? KDE users are still without any language selector in LightDM. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/803858 Title: No language chooser on login screen in LightDM Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in lightdm-gtk-greeter package in Ubuntu: Fix Released Bug description: LightDM doesn't appear to have a language selection choice in the Login screen, we need this to switch between Chinese and English for regular use, this feature is present in GDM, and we are really want to have it in LightDm as well, including correct setup of the zh_CN.utf-8 locale. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/803858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
patpat's fixed initramfs (INITRD_N11.2.GZ) doesn't work in ubuntu 15.10, system crash when trying launch ipconfig. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up Status in klibc package in Ubuntu: Confirmed Status in klibc package in Debian: New Bug description: Attempting to PXE boot both the 12.04.3 and 14.04 Live images. PXE boot works normally (PXE Menu, select desired image, image begins loading), then the boot process hangs while IP-Config attempts to get an IP address: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 2 secs - giving up IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 3 secs - giving up These lines appear very quickly (5 seconds has NOT elapsed), after about a minute, we get this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 4 secs - giving up Some time later, this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 6 secs - giving up Until finally, this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 9 secs - giving up IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: eth0 guessed broadcast address 172.25.11.31 IP-Config: eth0 complete (dhcp from 172.25.10.20): (snip) While watching the DHCP server logs, Ubuntu is either not sending a DHCP Discover at times, or is not replying back with a DHCPRequest during these sessions, presumably ignoring an response from the DHCP server. From the initial booting of the system via PXE, to when Ubuntu finally shows the desktop, almost 12 minutes will have elapsed. I am seeing this same behavior on both 12.04.3 and 14.04. After finding a number of similar erros via Google and no real resolution, I have opened this bug. The system experiencing this issue has multiple ethernet interfaces (actual HW, not a VM), some Google found solutions suggest hard coding DEVICE=eth0 in /etc/initramfs-tools/initramfs.conf, however this isn't acceptable as a system attempting to PXE boot may be using an alternate port for the network. I have found what looks to be a very similar bug filed for Debian, #584583, which also contains a patch for this issue (under Debian). I have no problems in PXE booting to various Windows, RedHat, Centos, or Fedora OSs. Ubuntu is the only Live OS that I'm attempting to boot at present. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.340 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Jun 6 20:22:09 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433155] [NEW] bash kill -l builtin gives wrong numbers for SIGRTMIN+n signals
Public bug reported: The command grep SIGRTMIN /usr/include/ -r gives me /usr/include/asm/signal.h:#define SIGRTMIN 32 and a bunch of other defines with the same value. But if I ask bash's kill builtin via kill -l, I get 34) SIGRTMIN. What's interesting, there's actually no number 32 listed at all. Number 34 goes right after 31, where the right 32 should appear. The other names defined via SIGRTMIN are also wrong. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: bash 4.2-2ubuntu2.6 ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66 Uname: Linux 3.2.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Mar 17 18:34:25 2015 InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120423) MarkForUpload: True ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1433155 Title: bash kill -l builtin gives wrong numbers for SIGRTMIN+n signals Status in bash package in Ubuntu: New Bug description: The command grep SIGRTMIN /usr/include/ -r gives me /usr/include/asm/signal.h:#define SIGRTMIN 32 and a bunch of other defines with the same value. But if I ask bash's kill builtin via kill -l, I get 34) SIGRTMIN. What's interesting, there's actually no number 32 listed at all. Number 34 goes right after 31, where the right 32 should appear. The other names defined via SIGRTMIN are also wrong. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: bash 4.2-2ubuntu2.6 ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66 Uname: Linux 3.2.0-76-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Mar 17 18:34:25 2015 InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120423) MarkForUpload: True ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1433155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 531208]
There's a project (created by me) which tries to work around this limitation of X by providing a daemon-like app intercepting Ctrl+Shift+U and allowing to enter UTF-32 character codes: https://gitorious.org/ucode/ucode/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/531208 Title: Need way to insert arbitrary unicode characters in Kubuntu Status in X.Org X server: Confirmed Status in “xorg” package in Ubuntu: Won't Fix Bug description: KDE, Qt, and Xorg are in disagreement about who should implement ISO 14755, which would facilitate the input of arbitrary unicode characters. This is the original KDE bug: https://bugs.kde.org/show_bug.cgi?id=103788 It was pushed upstream to Qt: http://bugreports.qt.nokia.com/browse/QTBUG-8 From there it was pushed further upstream to Xorg: https://bugs.freedesktop.org/show_bug.cgi?id=26747 Xorg pushes the bug downstream, back to either Qt or KDE to implement, just as Gnome implemented the fix themselves. An Xorg developer who does not want to be named says that if KDE won't implement it then my distro should. So here I file that request. Note that in KDE 3 one could use the Kcharselect applet to enter arbitrary unicode characters, however that has been disabled in KDE 4: https://bugs.kde.org/show_bug.cgi?id=190776 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/531208/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1342341] Re: upowerd kills USB performance
Also, writing back the default values to the /proc/sys/vm/... files doesn't fix the problem — so far only reboot with avoiding writing bad values helped. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1342341 Title: upowerd kills USB performance Status in “upower” package in Ubuntu: New Bug description: After launching Kubuntu and logging in to KDE I mount a USB storage device to e.g. /mnt/tmp and try the following command: dd if=/dev/zero of=/mnt/tmp/testfile bs=16M count=100 I don't wait until it finishes, because when I press Ctrl+C, it waits several more seconds and prints that it has copied only one record and the speed was from 200 kB/s to 1.8MB/s, which is nowhere near the speed the device can operate. On the other hand, if I rename /usr/lib/upower/upowerd and restart, the same command finishes in under a minute and says the speed was 30MB/s for USB3 and ~30MB/s for USB2 devices/ports. This hasn't happened on Kubuntu 12.04, but does happen on 14.04. Running powertop at the Tunables tab doesn't show any difference, so it doesn't look related to autosuspend or similar things. This also happens with Kubuntu 14.04 LiveCD, not only with the already installed system. I've tested this with 3 different USB devices: Transcend JF780 16GB (in USB 3.0 and 2.0 ports), OCZ ATV 8GB (USB 2.0 device) and Seagate SRD00F2 2TB (in USB 3.0 and 2.0 ports) with identical results. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upower 0.9.23-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: KDE Date: Wed Jul 16 00:29:34 2014 InstallationDate: Installed on 2014-05-26 (50 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1342341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1342341] Re: upowerd kills USB performance
This appears to be because upowerd calls `pm-powersave false`, which in turn activates /usr/lib/pm-utils/power.d/laptop-mode, which writes 10 and 5 to /proc/sys/vm/dirty_ratio and /proc/sys/vm/dirty_background_ratio, respectively, replacing default 20 and 10. Commenting this line in laptop-mode file works around this bug. Now I'm not sure whether this bug is a kernel bug or a pm-utils one. It seems definitely not a upower bug. BTW, this bug doesn't appear on another machine I tested it on, with GA- I915G-MF motherboard, while it appears on the problematic motherboard MSI B85-G41 PC Mate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1342341 Title: upowerd kills USB performance Status in “upower” package in Ubuntu: New Bug description: After launching Kubuntu and logging in to KDE I mount a USB storage device to e.g. /mnt/tmp and try the following command: dd if=/dev/zero of=/mnt/tmp/testfile bs=16M count=100 I don't wait until it finishes, because when I press Ctrl+C, it waits several more seconds and prints that it has copied only one record and the speed was from 200 kB/s to 1.8MB/s, which is nowhere near the speed the device can operate. On the other hand, if I rename /usr/lib/upower/upowerd and restart, the same command finishes in under a minute and says the speed was 30MB/s for USB3 and ~30MB/s for USB2 devices/ports. This hasn't happened on Kubuntu 12.04, but does happen on 14.04. Running powertop at the Tunables tab doesn't show any difference, so it doesn't look related to autosuspend or similar things. This also happens with Kubuntu 14.04 LiveCD, not only with the already installed system. I've tested this with 3 different USB devices: Transcend JF780 16GB (in USB 3.0 and 2.0 ports), OCZ ATV 8GB (USB 2.0 device) and Seagate SRD00F2 2TB (in USB 3.0 and 2.0 ports) with identical results. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upower 0.9.23-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: KDE Date: Wed Jul 16 00:29:34 2014 InstallationDate: Installed on 2014-05-26 (50 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1342341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1342341] Re: upowerd kills USB performance
In fact, it seems enough to write any value, even default+1, i.e. 21 to /proc/sys/vm/dirty_ratio to trigger the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1342341 Title: upowerd kills USB performance Status in “upower” package in Ubuntu: New Bug description: After launching Kubuntu and logging in to KDE I mount a USB storage device to e.g. /mnt/tmp and try the following command: dd if=/dev/zero of=/mnt/tmp/testfile bs=16M count=100 I don't wait until it finishes, because when I press Ctrl+C, it waits several more seconds and prints that it has copied only one record and the speed was from 200 kB/s to 1.8MB/s, which is nowhere near the speed the device can operate. On the other hand, if I rename /usr/lib/upower/upowerd and restart, the same command finishes in under a minute and says the speed was 30MB/s for USB3 and ~30MB/s for USB2 devices/ports. This hasn't happened on Kubuntu 12.04, but does happen on 14.04. Running powertop at the Tunables tab doesn't show any difference, so it doesn't look related to autosuspend or similar things. This also happens with Kubuntu 14.04 LiveCD, not only with the already installed system. I've tested this with 3 different USB devices: Transcend JF780 16GB (in USB 3.0 and 2.0 ports), OCZ ATV 8GB (USB 2.0 device) and Seagate SRD00F2 2TB (in USB 3.0 and 2.0 ports) with identical results. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upower 0.9.23-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: KDE Date: Wed Jul 16 00:29:34 2014 InstallationDate: Installed on 2014-05-26 (50 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1342341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1342341] [NEW] upowerd kills USB performance
Public bug reported: After launching Kubuntu and logging in to KDE I mount a USB storage device to e.g. /mnt/tmp and try the following command: dd if=/dev/zero of=/mnt/tmp/testfile bs=16M count=100 I don't wait until it finishes, because when I press Ctrl+C, it waits several more seconds and prints that it has copied only one record and the speed was from 200 kB/s to 1.8MB/s, which is nowhere near the speed the device can operate. On the other hand, if I rename /usr/lib/upower/upowerd and restart, the same command finishes in under a minute and says the speed was 30MB/s for USB3 and ~30MB/s for USB2 devices/ports. This hasn't happened on Kubuntu 12.04, but does happen on 14.04. Running powertop at the Tunables tab doesn't show any difference, so it doesn't look related to autosuspend or similar things. This also happens with Kubuntu 14.04 LiveCD, not only with the already installed system. I've tested this with 3 different USB devices: Transcend JF780 16GB (in USB 3.0 and 2.0 ports), OCZ ATV 8GB (USB 2.0 device) and Seagate SRD00F2 2TB (in USB 3.0 and 2.0 ports) with identical results. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upower 0.9.23-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: KDE Date: Wed Jul 16 00:29:34 2014 InstallationDate: Installed on 2014-05-26 (50 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1342341 Title: upowerd kills USB performance Status in “upower” package in Ubuntu: New Bug description: After launching Kubuntu and logging in to KDE I mount a USB storage device to e.g. /mnt/tmp and try the following command: dd if=/dev/zero of=/mnt/tmp/testfile bs=16M count=100 I don't wait until it finishes, because when I press Ctrl+C, it waits several more seconds and prints that it has copied only one record and the speed was from 200 kB/s to 1.8MB/s, which is nowhere near the speed the device can operate. On the other hand, if I rename /usr/lib/upower/upowerd and restart, the same command finishes in under a minute and says the speed was 30MB/s for USB3 and ~30MB/s for USB2 devices/ports. This hasn't happened on Kubuntu 12.04, but does happen on 14.04. Running powertop at the Tunables tab doesn't show any difference, so it doesn't look related to autosuspend or similar things. This also happens with Kubuntu 14.04 LiveCD, not only with the already installed system. I've tested this with 3 different USB devices: Transcend JF780 16GB (in USB 3.0 and 2.0 ports), OCZ ATV 8GB (USB 2.0 device) and Seagate SRD00F2 2TB (in USB 3.0 and 2.0 ports) with identical results. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upower 0.9.23-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: KDE Date: Wed Jul 16 00:29:34 2014 InstallationDate: Installed on 2014-05-26 (50 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.1) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1342341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
