[Desktop-packages] [Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
I have similar problem. Acer Aspire VN7-792G with Nvida GeForce 960M and Ubuntu 18.04.2 LTS. Try to connect to monitor Asus vx239h. Sometimes it turns out to connect a second screen as an extension of the screen, for example, if you go into console mode and return. It works for a while, when you try to enter Settings, the screen turns off. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in xorg-server package in Ubuntu: Incomplete Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-2 disconnected (normal left inverted right x axis y axis) 1920x1080 (0x258) 148.500MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.50KHz v: height 1080 start 1084 end 1089 total 1125 clock 60.00Hz 1920x1080 (0x259) 148.500MHz +HSync +VSync h: width 1920 start 2448 end 2492 total 2640 skew0 clock 56.25KHz v: height 1080 start 1084 end 1089 total 1125 clock 50.00Hz 1920x1080 (0x25a) 148.352MHz +HSync +VSync h: width 1920 start 2008 end 2052 total 2200 skew0 clock 67.43KHz v: height 1080 start 1084 end 1089 total 1125
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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&interface=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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776479] [NEW] package nvidia-prime 0.8.8 failed to install/upgrade: there is no script in the new version of the package - giving up
Public bug reported: I was doing an upgrade from 16.04 to 18.04 by `do-release-upgrade -d`, and after finishing install, on startup I was presented with a bug dialog suggesting me to make this bug report. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.8 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 12:37:11 2018 Dependencies: ErrorMessage: there is no script in the new version of the package - giving up InstallationDate: Installed on 2012-03-23 (2271 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: nvidia-prime Title: package nvidia-prime 0.8.8 failed to install/upgrade: there is no script in the new version of the package - giving up UpgradeStatus: Upgraded to bionic on 2018-06-12 (0 days ago) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1776479 Title: package nvidia-prime 0.8.8 failed to install/upgrade: there is no script in the new version of the package - giving up Status in nvidia-prime package in Ubuntu: New Bug description: I was doing an upgrade from 16.04 to 18.04 by `do-release-upgrade -d`, and after finishing install, on startup I was presented with a bug dialog suggesting me to make this bug report. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.8 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 12:37:11 2018 Dependencies: ErrorMessage: there is no script in the new version of the package - giving up InstallationDate: Installed on 2012-03-23 (2271 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: nvidia-prime Title: package nvidia-prime 0.8.8 failed to install/upgrade: there is no script in the new version of the package - giving up UpgradeStatus: Upgraded to bionic on 2018-06-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1776479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245473] Re: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program
In Kubuntu 18.04 with latest updates still can't use Ctrl+Shift because hotkeys can't work properly . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Settings Daemon: Fix Released Status in GNOME Shell: Won't Fix Status in Unity: Confirmed Status in X.Org X server: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-settings-daemon package in Debian: New Status in gnome-settings-daemon package in Fedora: In Progress Status in gnome-settings-daemon package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
Solution #79 solves the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB Status in nautilus package in Ubuntu: Confirmed Bug description: Hi While copying many and large files to and from a USB drive, the system becomes incredibly slow and sometimes hangs. I watched the system monitor while it was running slowly but cpu was not above 50% at any time, the same for memory. I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD" laptop. Description: Ubuntu 13.04 Release: 13.04 nautilus: Installed: 1:3.6.3-0ubuntu16 Candidate: 1:3.6.3-0ubuntu16 Version table: *** 1:3.6.3-0ubuntu16 0 500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Aquire many large files (like your totally legit moviecollection) 2) Copy files to external HD 3) Open your browser and be sad when your system becomes incredibly slow after a few minutes This is my first bugreport so if I'm missing something, please tell me. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Aug 6 22:56:34 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-05-31 (67 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1208993/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745272] [NEW] package libsane1 1.0.27-1~experimental3ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth
Public bug reported: this bug ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Thu Jan 25 09:12:28 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental3ubuntu1 Unpacking libsane1:i386 (1.0.27-1~experimental3ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-fAO2gq/27-libsane1_1.0.27-1~experimental3ubuntu1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2017-12-08 (47 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171207) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental3ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1745272 Title: package libsane1 1.0.27-1~experimental3ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: New Bug description: this bug ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Thu Jan 25 09:12:28 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental3ubuntu1 Unpacking libsane1:i386 (1.0.27-1~experimental3ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-fAO2gq/27-libsane1_1.0.27-1~experimental3ubuntu1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2017-12-08 (47 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171207) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental3ubuntu1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1745272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741671] Re: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory t
Martin's solution worked for me $ uname -r 4.13.0-26-generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1741671 Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build [nv-linux.h:199:2: error: #error "This driver requires the ability to change memory types!"] Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: not compiling after installation of linux-image-4.13.0-21-generic ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-340 340.102-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.102 Mon Jan 16 13:06:29 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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 DKMSKernelVersion: 4.13.0-21-generic Date: Sat Jan 6 18:36:58 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: dkms:nvidia-340:340.102-0ubuntu0.16.04.2:/var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:199:2: error: #error "This driver requires the ability to change memory types!" GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c] InstallationDate: Installed on 2016-04-26 (619 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC PackageVersion: 340.102-0ubuntu0.16.04.2 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-97-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.102-0ubuntu0.16.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 363C dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039E202413102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 039E202413102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Jan 6 18:17:29 2018 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1741671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573206] Re: GNOME Software does not install third-party .deb packages
*** This bug is a duplicate of bug 1573408 *** https://bugs.launchpad.net/bugs/1573408 Just installed Ubuntu Studio 16.04.3, also affects me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1573206 Title: GNOME Software does not install third-party .deb packages Status in gdebi: New Status in GNOME Software: New Status in GRadio: New Status in SoundConverter: New Status in Ubuntu GNOME: Triaged Status in Ubuntu Studio: Triaged Status in gnome-software package in Ubuntu: Triaged Bug description: Ubuntu 16.04 LTS (clean install). 64-bit. Final release. Gnome-software version: 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 Version table: *** 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 500 500 http://no.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status I intended to install MEGA Sync Client, Google Chrome and Dropbox by downloading the needed packages from their websites (respectively https://mega.nz/#sync and https://www.google.com/chrome/ and https://www.dropbox.com/install?os=lnx ). I opened the packages one by one with gnome-software and pressed Install - nothing, except for a super-quick progress bar animation, happened. No matter how many times I tried, same result. Also, an icon pops up on the panel saying "Waiting to install", but nothing seems to happen. This only seems to happen with third-party packages; installing a random deb from packages.ubuntu.com/xenial worked. I even tried to reinstall the system to make this work, but same problem. Gdebi, however, installs the packages as expected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160420.1.ca63436.ubuntu-xenial-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 21 21:01:52 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2016-04-21 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=nn_NO:nn:no_NO:no:nb_NO:nb:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nn_NO.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdebi/+bug/1573206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1168197] Re: 'USB Keyboard+Smartpad' not detected as touchpad in 'Samsung Ativ Smart PC Pro 700t'
Touchpad still not recognized, using 4.9.16 kernerl -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1168197 Title: 'USB Keyboard+Smartpad' not detected as touchpad in 'Samsung Ativ Smart PC Pro 700t' Status in xserver-xorg-input-synaptics package in Ubuntu: Expired Bug description: The touchpad on the detachable base for the 'Samsung Ativ Smart PC Pro 700t' is not detected as a touchpad. The 'Touchpad' tab in 'Mouse and Touchpad' settings is missing. The keyboard works fine and the touchpad works as a mouse (moving the cursor, clicking the left and right buttons). Tap to click also works, however scrolling does not on either the edge or with two fingers. I am uncertain of the manufacturer of the touchpad as it is not listed clearly anywhere, however I suspect it is "Elan Microelectronics Corp" as this is listed under lsusb, they make touchpads, and the entry disappears when the base is detached. Nothing related appears under lspci or lshw. This is the first time ubuntu has been installed on this machine and the touchpad has never worked correctly. Any use of synclient outputs: "Couldn't find synaptics properties. No synaptics driver loaded?" Ubuntu 12.10. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu5 [modified: usr/share/X11/xorg.conf.d/50-synaptics.conf] ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6 Uname: Linux 3.5.0-26-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Thu Apr 11 17:21:14 2013 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu InstallationDate: Installed on 2013-03-28 (14 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: SAMSUNG ELECTRONICS CO., LTD. 700T1C MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-26-generic.efi.signed root=UUID=ca9ed351-4c7e-4b31-9ca3-eb81bccc190d ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06AAT.038.130219.dg dmi.board.asset.tag: No Asset Tag dmi.board.name: XE700T1C-A02US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 8 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06AAT.038.130219.dg:bd02/19/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn700T1C:pvrP06AAT:rvnSAMSUNGELECTRONICSCO.,LTD.:rnXE700T1C-A02US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct8:cvrN/A: dmi.product.name: 700T1C dmi.product.version: P06AAT dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.8.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1168197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1674085] [NEW] package libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: пакет libreoffice-core уже установлен и настроен
Public bug reported: error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial1 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Mar 19 14:23:23 2017 ErrorMessage: пакет libreoffice-core уже установлен и настроен InstallationDate: Installed on 2017-03-19 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: libreoffice Title: package libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: пакет libreoffice-core уже установлен и настроен UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1674085 Title: package libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: пакет libreoffice-core уже установлен и настроен Status in libreoffice package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial1 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Mar 19 14:23:23 2017 ErrorMessage: пакет libreoffice-core уже установлен и настроен InstallationDate: Installed on 2017-03-19 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: libreoffice Title: package libreoffice-core 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: пакет libreoffice-core уже установлен и настроен UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1674085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1674084] [NEW] package libreoffice-avmedia-backend-gstreamer 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: пакет libreoffice-avmedia-backend-gstreamer уже установлен
Public bug reported: ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-avmedia-backend-gstreamer 1:5.1.6~rc2-0ubuntu1~xenial1 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Mar 19 14:23:23 2017 ErrorMessage: пакет libreoffice-avmedia-backend-gstreamer уже установлен и настроен InstallationDate: Installed on 2017-03-19 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: libreoffice Title: package libreoffice-avmedia-backend-gstreamer 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: пакет libreoffice-avmedia-backend-gstreamer уже установлен и настроен UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1674084 Title: package libreoffice-avmedia-backend-gstreamer 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: пакет libreoffice-avmedia-backend-gstreamer уже установлен и настроен Status in libreoffice package in Ubuntu: New Bug description: ? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-avmedia-backend-gstreamer 1:5.1.6~rc2-0ubuntu1~xenial1 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Mar 19 14:23:23 2017 ErrorMessage: пакет libreoffice-avmedia-backend-gstreamer уже установлен и настроен InstallationDate: Installed on 2017-03-19 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: libreoffice Title: package libreoffice-avmedia-backend-gstreamer 1:5.1.6~rc2-0ubuntu1~xenial1 failed to install/upgrade: пакет libreoffice-avmedia-backend-gstreamer уже установлен и настроен UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1674084/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1314556] Re: Unable to mount Android MTP device
In general, to begin finding what application takes your Android device, try the following command: sudo lsof | grep /usb/ This should give you some pointers to processes using files in e.g. /dev/bus/usb/. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1314556 Title: Unable to mount Android MTP device Status in gvfs package in Ubuntu: Confirmed Bug description: I have the same problem on 3 computers with 14.04: So I tried, mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10 Attempting to connect device(s) ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): Resource temporarily unavailable outep: usb_get_endpoint_status(): Device or resource busy ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gvfs-backends 1.20.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 30 11:18:12 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfs-mtp-volume-monitor InstallationDate: Installed on 2013-02-12 (441 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gvfs UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1314556] Re: Unable to mount Android MTP device
For KDE users experiencing a similar issue, make sure that either Amarok isn't running or its MTP plugin is disabled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1314556 Title: Unable to mount Android MTP device Status in gvfs package in Ubuntu: Confirmed Bug description: I have the same problem on 3 computers with 14.04: So I tried, mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP). Found 1 device(s): Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 10 Attempting to connect device(s) ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device inep: usb_get_endpoint_status(): Resource temporarily unavailable outep: usb_get_endpoint_status(): Device or resource busy ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gvfs-backends 1.20.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 30 11:18:12 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfs-mtp-volume-monitor InstallationDate: Installed on 2013-02-12 (441 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gvfs UpgradeStatus: Upgraded to trusty on 2014-04-02 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1566513] [NEW] Complex numbers are exponentiated incorrectly
Public bug reported: The calculator incorrectly performs exponentiation if the base is complex and the exponent is a positive integer. Under these conditions the calculator exponentiates the real part of the base and leaves its imaginary part intact, that does not agree with the complex numbers operation rules. If the exponent is not a positive integer, the calculation is performed correctly. Steps to reproduce the bug: 1. Start the program. 2. Evaluate expression "i^2". The displayed result is "i". 3. Evaluate expression "(1+i)^2". The displayed result is "1+i". 4. Evaluate expression "(2+i)^2". The displayed result is "4+i". Please find a quick fix patch attached. I did not study its comprehensiveness and optimality, but it seems to work. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-calculator 1:3.16.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 5 22:59:29 2016 InstallationDate: Installed on 2014-09-29 (554 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gnome-calculator UpgradeStatus: Upgraded to wily on 2015-10-29 (159 days ago) ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Patch added: "complex-exponentiation.patch" https://bugs.launchpad.net/bugs/1566513/+attachment/4625159/+files/complex-exponentiation.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1566513 Title: Complex numbers are exponentiated incorrectly Status in gnome-calculator package in Ubuntu: New Bug description: The calculator incorrectly performs exponentiation if the base is complex and the exponent is a positive integer. Under these conditions the calculator exponentiates the real part of the base and leaves its imaginary part intact, that does not agree with the complex numbers operation rules. If the exponent is not a positive integer, the calculation is performed correctly. Steps to reproduce the bug: 1. Start the program. 2. Evaluate expression "i^2". The displayed result is "i". 3. Evaluate expression "(1+i)^2". The displayed result is "1+i". 4. Evaluate expression "(2+i)^2". The displayed result is "4+i". Please find a quick fix patch attached. I did not study its comprehensiveness and optimality, but it seems to work. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-calculator 1:3.16.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 5 22:59:29 2016 InstallationDate: Installed on 2014-09-29 (554 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gnome-calculator UpgradeStatus: Upgraded to wily on 2015-10-29 (159 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1566513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1408614] Re: eclipse crashes in Ubuntu 14.04 when using oxygen-gtk theme
This is a bug in GTK2: https://bugzilla.gnome.org/show_bug.cgi?id=736323 See this KDE bug report for more details: https://bugs.kde.org/show_bug.cgi?id=329814 ** Bug watch added: GNOME Bug Tracker #736323 https://bugzilla.gnome.org/show_bug.cgi?id=736323 ** Bug watch added: KDE Bug Tracking System #329814 https://bugs.kde.org/show_bug.cgi?id=329814 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1408614 Title: eclipse crashes in Ubuntu 14.04 when using oxygen-gtk theme Status in gtk2-engines-oxygen package in Ubuntu: New Bug description: eclipse crashes in Ubuntu 14.04 when using oxygen-gtk theme (which AFAIK is the default when running eclipse under KDE). Steps to reproduce: env GTK2_RC_FILES=/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc eclipse - Open the properties dialog for a project - Close the dialog Result: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7ff89e26d718, pid=9825, tid=140706574657280 # # JRE version: OpenJDK Runtime Environment (7.0_65-b32) (build 1.7.0_65-b32) # Java VM: OpenJDK 64-Bit Server VM (24.65-b04 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea 2.5.3 # Distribution: Ubuntu 14.04 LTS, package 7u71-2.5.3-0ubuntu0.14.04.1 # Problematic frame: # C [libgobject-2.0.so.0+0x19718] g_object_get_qdata+0x18 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/kiesssn/hs_err_pid9825.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # http://icedtea.classpath.org/bugzilla # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # Package versions: ii eclipse 3.8.1-5.1 all Extensible Tool Platform and Java IDE ii gtk2-engines-oxygen:amd64 1.4.5-0ubuntu1 amd64Oxygen widget theme for GTK+-based applications Adding this line to the end of ~/.gtkrc-2.0 will fix (or workaround) the problem (unless GTK2_RC_FILES is set and the file is not read): style "oxygen-default" { GtkComboBox::appears-as-list = 0 } Setting GtkComboBox::appears-as-list in /usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc to 0 also works. Related bug reports: https://bugzilla.gnome.org/show_bug.cgi?id=736323 https://bugs.eclipse.org/bugs/show_bug.cgi?id=372560 http://askubuntu.com/questions/513471/kubuntu-14-04eclipse-adt-crashes-at-button-ok-from-project-properties To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/1408614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242801]
*** Bug 341321 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1242801 Title: meld assertion while selecting directory Status in Oxygen-gtk: Won't Fix Status in gtk2-engines-oxygen package in Ubuntu: Invalid Bug description: I installed saucy with version 1.3.4-0ubuntu1 of gtk2-engines-oxygen and meld version 1.8.2 on Kubuntu/KDE. - set GTK2 theme to oxygen-gtk in system settings - Start meld - on start screen (new comparsion) select directory comparison - select in either source or destination directory combo box the entry 'Other...' - crash in the terminal i could see the callstack of the crash: /usr/bin/meld:167: GtkWarning: gtk_tree_model_filter_get_value: assertion 'GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed gtk.main() /usr/bin/meld:167: Warning: /build/buildd/glib2.0-2.38.0/./gobject/gtype.c:4215: type id '0' is invalid gtk.main() /usr/bin/meld:167: Warning: can't peek value table for type '' which is not currently referenced gtk.main() Segmentation fault I also tried with version 1.4.0-0ubuntu1 of gtk2-engines-oxygen with the same result. If I select a QtCurve as gtk2 theme the same crash occurs. If i select a different theme (e.g. Clearlooks) i get the file dialog and everything is ok. Today i tested this issue on a raring machine and i was unable to reproduce this issue there. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk2-engines-oxygen/+bug/1242801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1391531] Re: 'src/animations/oxygencomboboxdata.cpp:87:void Oxygen::ComboBoxData::setButton(GtkWidget*): "!_button._widget" assertion failed' crashes Eclipse Luna
** Also affects: gtk2-engines-oxygen via https://bugs.kde.org/show_bug.cgi?id=339174 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1391531 Title: 'src/animations/oxygencomboboxdata.cpp:87:void Oxygen::ComboBoxData::setButton(GtkWidget*): "!_button._widget" assertion failed' crashes Eclipse Luna Status in Oxygen-gtk: Unknown Status in “gtk2-engines-oxygen” package in Ubuntu: Confirmed Bug description: Eclipse crashed after doing some work using Eclipse CDT from upstream website. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gtk2-engines-oxygen 1.4.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 11 22:10:22 2014 InstallationDate: Installed on 2014-11-10 (0 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=zh_TW:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_TW.UTF-8 SHELL=/bin/bash SourcePackage: gtk2-engines-oxygen UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk2-engines-oxygen/+bug/1391531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1395778] Re: Not apply icon themes in GTK-apps
Could you report it to bugs.kde.org? Few KDE developers look at Launchpad bug reports. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1395778 Title: Not apply icon themes in GTK-apps Status in “gtk2-engines-oxygen” package in Ubuntu: New Bug description: Kubuntu: 14.04 KDE: 4.14.2 gtk2-engines-oxygen: 1.4.5 In Gtk-apps (Gimp, Firefox etc...) show only Gnome-icon theme. Other icon themes not apply! ~/.gtkrc-2.0: # File created by KDE Gtk Config # Configs for GTK2 programs include "/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc" style "user-font" { font_name="Liberation Sans Regular" } widget_class "*" style "user-font" gtk-font-name="Liberation Sans Regular 10" gtk-theme-name="oxygen-gtk" gtk-icon-theme-name="KFaenza" gtk-fallback-icon-theme="oxygen" gtk-toolbar-style=GTK_TOOLBAR_ICONS gtk-menu-images=0 gtk-button-images=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/1395778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242801]
In gtk3 the file is another: /usr/share/themes/oxygen- gtk/gtk-3.0/gtk.css -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1242801 Title: meld assertion while selecting directory Status in Oxygen-gtk: Won't Fix Status in “gtk2-engines-oxygen” package in Ubuntu: Invalid Bug description: I installed saucy with version 1.3.4-0ubuntu1 of gtk2-engines-oxygen and meld version 1.8.2 on Kubuntu/KDE. - set GTK2 theme to oxygen-gtk in system settings - Start meld - on start screen (new comparsion) select directory comparison - select in either source or destination directory combo box the entry 'Other...' - crash in the terminal i could see the callstack of the crash: /usr/bin/meld:167: GtkWarning: gtk_tree_model_filter_get_value: assertion 'GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed gtk.main() /usr/bin/meld:167: Warning: /build/buildd/glib2.0-2.38.0/./gobject/gtype.c:4215: type id '0' is invalid gtk.main() /usr/bin/meld:167: Warning: can't peek value table for type '' which is not currently referenced gtk.main() Segmentation fault I also tried with version 1.4.0-0ubuntu1 of gtk2-engines-oxygen with the same result. If I select a QtCurve as gtk2 theme the same crash occurs. If i select a different theme (e.g. Clearlooks) i get the file dialog and everything is ok. Today i tested this issue on a raring machine and i was unable to reproduce this issue there. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk2-engines-oxygen/+bug/1242801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242801]
(In reply to Lastique from comment #22) > Is it possible to package oxygen-gtk with the updated config as in comment > 11 so that users are not affected until the upstream bug is fixed? This setting is purposefully set to 1 to achieve the look of combobox dropdown lists as they should be. Otherwise you'll have menus instead of lists, which are uglier, harder to navigate and inconsistent with oxygen-qt. So no, this won't be packaged as is. An option would be to devise an in-code workaround precisely for meld (which I guess won't go into official oxygen-gtk), but I don't have time to do this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1242801 Title: meld assertion while selecting directory Status in Oxygen-gtk: Won't Fix Status in “gtk2-engines-oxygen” package in Ubuntu: Invalid Bug description: I installed saucy with version 1.3.4-0ubuntu1 of gtk2-engines-oxygen and meld version 1.8.2 on Kubuntu/KDE. - set GTK2 theme to oxygen-gtk in system settings - Start meld - on start screen (new comparsion) select directory comparison - select in either source or destination directory combo box the entry 'Other...' - crash in the terminal i could see the callstack of the crash: /usr/bin/meld:167: GtkWarning: gtk_tree_model_filter_get_value: assertion 'GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed gtk.main() /usr/bin/meld:167: Warning: /build/buildd/glib2.0-2.38.0/./gobject/gtype.c:4215: type id '0' is invalid gtk.main() /usr/bin/meld:167: Warning: can't peek value table for type '' which is not currently referenced gtk.main() Segmentation fault I also tried with version 1.4.0-0ubuntu1 of gtk2-engines-oxygen with the same result. If I select a QtCurve as gtk2 theme the same crash occurs. If i select a different theme (e.g. Clearlooks) i get the file dialog and everything is ok. Today i tested this issue on a raring machine and i was unable to reproduce this issue there. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk2-engines-oxygen/+bug/1242801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1391531] Re: 'src/animations/oxygencomboboxdata.cpp:87:void Oxygen::ComboBoxData::setButton(GtkWidget*): "!_button._widget" assertion failed' crashes Eclipse Luna
This is fixed upstream: https://bugs.kde.org/show_bug.cgi?id=339174 ** Bug watch added: KDE Bug Tracking System #339174 https://bugs.kde.org/show_bug.cgi?id=339174 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1391531 Title: 'src/animations/oxygencomboboxdata.cpp:87:void Oxygen::ComboBoxData::setButton(GtkWidget*): "!_button._widget" assertion failed' crashes Eclipse Luna Status in “gtk2-engines-oxygen” package in Ubuntu: New Bug description: Eclipse crashed after doing some work using Eclipse CDT from upstream website. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gtk2-engines-oxygen 1.4.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 11 22:10:22 2014 InstallationDate: Installed on 2014-11-10 (0 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=zh_TW:zh PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=zh_TW.UTF-8 SHELL=/bin/bash SourcePackage: gtk2-engines-oxygen UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/1391531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364323] [NEW] package tex-common 4.04 failed to install/upgrade: ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Public bug reported: During upgrade of Kubuntu 12.04 to 14.04 the system reports an error concerning package tex-common. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tex-common 4.04 ProcVersionSignature: Ubuntu 3.2.0-39.62-generic 3.2.39 Uname: Linux 3.2.0-39-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.7 Architecture: amd64 Date: Tue Sep 2 14:52:22 2014 ErrorMessage: ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True PackageArchitecture: all SourcePackage: tex-common Title: package tex-common 4.04 failed to install/upgrade: ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: Upgraded to trusty on 2014-09-02 (0 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1364323 Title: package tex-common 4.04 failed to install/upgrade: ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in “tex-common” package in Ubuntu: New Bug description: During upgrade of Kubuntu 12.04 to 14.04 the system reports an error concerning package tex-common. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tex-common 4.04 ProcVersionSignature: Ubuntu 3.2.0-39.62-generic 3.2.39 Uname: Linux 3.2.0-39-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.7 Architecture: amd64 Date: Tue Sep 2 14:52:22 2014 ErrorMessage: ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True PackageArchitecture: all SourcePackage: tex-common Title: package tex-common 4.04 failed to install/upgrade: ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: Upgraded to trusty on 2014-09-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1364323/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1358271] Re: Eclipse crashes with 'oxygen-gtk' theme enabled
What versions of Ubuntu, Eclipse, oxygen-gtk do you use? Please also install oxygen-gtk debug symbols (or oxygen-gtk itself from sources at [1]) and post the backtrace from crash. It'd also be useful if you describe how one should set up Eclipse to be able to reproduce the crash (I don't have any Android-related option in New Project dialog). [1]: https://projects.kde.org/projects/playground/artwork/oxygen- gtk/repository -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1358271 Title: Eclipse crashes with 'oxygen-gtk' theme enabled Status in “gtk2-engines-oxygen” package in Ubuntu: New Bug description: Every time I have Eclipse crashed when I create an Android project. After some investigations I discovered it is due to 'oxygen-gtk' theme. Eclipse works fine with others but I'd like it to look like native Qt apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/1358271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1246683] Re: Middle button does not work for scrolling
The script works perfectly on my t440p with kubuntu 14.04. Thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1246683 Title: Middle button does not work for scrolling Status in “xserver-xorg-input-evdev” package in Ubuntu: Incomplete Bug description: With my Lenovo T440s laptop the Trackpad/Trackpoint laptop scrolling does not work when pressing middle button + moving the Trackpoint. evdev seems to be set correctly ( http://paste.ubuntuusers.de/416732/ ). Middle button itself works fine for middle clicks just no scrolling. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 Uname: Linux 3.12.0-031200rc7-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 31 12:36:14 2013 InstallationDate: Installed on 2013-10-17 (13 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) MarkForUpload: True SourcePackage: xserver-xorg-input-evdev UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1246683/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1342341] Re: upowerd kills USB performance
It appears to be the kernel bug. Sort of. I've bisected the kernel to commit ab8fabd46f811d5153d8a0cd2fac9a0d41fb593d. There's a discussion of this problem in this thread: https://groups.google.com/forum/#!topic/linux.kernel/Jc69VRli3k0 This seems basically WONTFIX from linux side. But a workarounds are: 1. "vm.highmem_is_dirtyable=1" sysctl option — although this makes the performance not as high as it was in 3.2.x kernels, it at least allows one to use the disk subsystem 2. "mem=15G" kernel parameter limits the amount of usable memory, preventing the problems discussed in the thread I linked above 3. Use 64 bit kernel. This seems to be not a trivial thing to do with Ubuntu, but I may be wrong. But this is proposed as _the solution_. -- You received this bug notification because you are a member of Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-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 Desktop 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/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1242801]
@Lastique it's not our bug, so there's little sense in saying, that it's still present, at KDE bug tracker. See posts above, namely comment 11. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1242801 Title: meld assertion while selecting directory Status in Oxygen-gtk: Won't Fix Status in “gtk2-engines-oxygen” package in Ubuntu: Invalid Bug description: I installed saucy with version 1.3.4-0ubuntu1 of gtk2-engines-oxygen and meld version 1.8.2 on Kubuntu/KDE. - set GTK2 theme to oxygen-gtk in system settings - Start meld - on start screen (new comparsion) select directory comparison - select in either source or destination directory combo box the entry 'Other...' - crash in the terminal i could see the callstack of the crash: /usr/bin/meld:167: GtkWarning: gtk_tree_model_filter_get_value: assertion 'GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed gtk.main() /usr/bin/meld:167: Warning: /build/buildd/glib2.0-2.38.0/./gobject/gtype.c:4215: type id '0' is invalid gtk.main() /usr/bin/meld:167: Warning: can't peek value table for type '' which is not currently referenced gtk.main() Segmentation fault I also tried with version 1.4.0-0ubuntu1 of gtk2-engines-oxygen with the same result. If I select a QtCurve as gtk2 theme the same crash occurs. If i select a different theme (e.g. Clearlooks) i get the file dialog and everything is ok. Today i tested this issue on a raring machine and i was unable to reproduce this issue there. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk2-engines-oxygen/+bug/1242801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309132]
In fact, although the bug reproduces in current version, this crash log was generated with oxygen-gtk2 1.4.3-xxx (current version gives the same output). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1309132 Title: oxygen-gtk2 makes scilab crash Status in Oxygen-gtk: New Status in Scilab: In Progress Status in “gtk2-engines-oxygen” package in Ubuntu: Invalid Bug description: On kubuntu 13.10 64 bit, it is impossible to use scilab 5.5.0 (downloaded from the scilab site) if the appearance of gtk2 apps is set to oxygen-gtk. In this cases, scilab immediately crashes. Using others gtk engines, scilab 5.5.0 starts fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gtk2-engines-oxygen 1.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Apr 17 19:38:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2009-11-12 (1617 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True SourcePackage: gtk2-engines-oxygen UpgradeStatus: Upgraded to saucy on 2013-12-18 (120 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk2-engines-oxygen/+bug/1309132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309132]
Created attachment 86317 Crash log Indeed, it uses GTK2. I must have confused it with another app I tested. Here's the log printed at the moment of crash. @Hugo if you need some more info, please ask. I can't find much time to do actual debugging these days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1309132 Title: oxygen-gtk2 makes scilab crash Status in Oxygen-gtk: New Status in Scilab: In Progress Status in “gtk2-engines-oxygen” package in Ubuntu: Invalid Bug description: On kubuntu 13.10 64 bit, it is impossible to use scilab 5.5.0 (downloaded from the scilab site) if the appearance of gtk2 apps is set to oxygen-gtk. In this cases, scilab immediately crashes. Using others gtk engines, scilab 5.5.0 starts fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gtk2-engines-oxygen 1.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Apr 17 19:38:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2009-11-12 (1617 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True SourcePackage: gtk2-engines-oxygen UpgradeStatus: Upgraded to saucy on 2013-12-18 (120 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk2-engines-oxygen/+bug/1309132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309132]
Created attachment 86318 Backtrace from gdb Here's somewhat more verbose backtrace, taken from gdb. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1309132 Title: oxygen-gtk2 makes scilab crash Status in Oxygen-gtk: New Status in Scilab: In Progress Status in “gtk2-engines-oxygen” package in Ubuntu: Invalid Bug description: On kubuntu 13.10 64 bit, it is impossible to use scilab 5.5.0 (downloaded from the scilab site) if the appearance of gtk2 apps is set to oxygen-gtk. In this cases, scilab immediately crashes. Using others gtk engines, scilab 5.5.0 starts fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gtk2-engines-oxygen 1.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Apr 17 19:38:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2009-11-12 (1617 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True SourcePackage: gtk2-engines-oxygen UpgradeStatus: Upgraded to saucy on 2013-12-18 (120 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk2-engines-oxygen/+bug/1309132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309132] Re: oxygen-gtk2 makes scilab crash
Ah, and newer scilab seems to use not gtk2, but gtk3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1309132 Title: oxygen-gtk2 makes scilab crash Status in “gtk2-engines-oxygen” package in Ubuntu: Invalid Bug description: On kubuntu 13.10 64 bit, it is impossible to use scilab 5.5.0 (downloaded from the scilab site) if the appearance of gtk2 apps is set to oxygen-gtk. In this cases, scilab immediately crashes. Using others gtk engines, scilab 5.5.0 starts fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gtk2-engines-oxygen 1.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Apr 17 19:38:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2009-11-12 (1617 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True SourcePackage: gtk2-engines-oxygen UpgradeStatus: Upgraded to saucy on 2013-12-18 (120 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/1309132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309132] Re: oxygen-gtk2 makes scilab crash
@Sergio I actually was able to reproduce this even with Ubuntu Precise 64 bit. Please do report this to bugs.kde.org: I currently don't have much time to debug this, while Hugo (another upstream developer) might be able look into this. When reporting, please be sure to include terminal output of scilab when it crashes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1309132 Title: oxygen-gtk2 makes scilab crash Status in “gtk2-engines-oxygen” package in Ubuntu: Invalid Bug description: On kubuntu 13.10 64 bit, it is impossible to use scilab 5.5.0 (downloaded from the scilab site) if the appearance of gtk2 apps is set to oxygen-gtk. In this cases, scilab immediately crashes. Using others gtk engines, scilab 5.5.0 starts fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gtk2-engines-oxygen 1.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Thu Apr 17 19:38:52 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2009-11-12 (1617 days ago) InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True SourcePackage: gtk2-engines-oxygen UpgradeStatus: Upgraded to saucy on 2013-12-18 (120 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/1309132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1311744] [NEW] keyboard not working on this window
Public bug reported: Keyboard not working on window for add online account. On the application "Browser" also not working keyboard. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1 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 CurrentDesktop: Unity Date: Wed Apr 23 20:27:40 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2013-10-29 (176 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity-control-center SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to trusty on 2014-04-09 (14 days ago) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 gnome-control-center 1:3.6.3-0ubuntu56 ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1311744 Title: keyboard not working on this window Status in “unity-control-center” package in Ubuntu: New Bug description: Keyboard not working on window for add online account. On the application "Browser" also not working keyboard. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140410-0ubuntu1 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 CurrentDesktop: Unity Date: Wed Apr 23 20:27:40 2014 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2013-10-29 (176 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity-control-center SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: Upgraded to trusty on 2014-04-09 (14 days ago) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 gnome-control-center 1:3.6.3-0ubuntu56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1311744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1291461] Re: Unity Lockscreen - layout switching shortcuts not working
** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1291461 Title: Unity Lockscreen - layout switching shortcuts not working Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: New Unity Lockscreen has the same problem as the old one from Gnome: the chosen keyboard shortcut is not switching keyboard layouts on it, the only way is to use mouse. Steps to reproduce: 1. To make things uncomfortable, switch layout to Russian or any other with your favourite shortcut(i am using alt-shift) 2. Lock the screen with ctrl-alt-l 3. Try to change layout back to English to enter password Expected: Layput should change and you should be able to login without touching anything but keyboard. What's happening: Nothing, doesn't react on the keyboard shortcut, you have to change layout using indicator on top panel. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291461/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1002325] Re: SIGILL: chromium-browse[12042] trap invalid opcode ip:7f4e637e1c7d sp:7fff4a10d878 error:0 in chromium-browser
For the record, the illegal instruction which leads to crash appears to be UD2 for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1002325 Title: SIGILL: chromium-browse[12042] trap invalid opcode ip:7f4e637e1c7d sp:7fff4a10d878 error:0 in chromium-browser Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. $ chromium-browser --temp-profile # just to rule out custom configuration 2. Go to youtube.com/html5, opt in to html5 3. Go to http://www.youtube.com/watch_popup?v=-JryxdydOj0&vq=480 What happens: The tab goes Aw, Snap! and dmesg says "chromium-browse[12042] trap invalid opcode ip:7f4e637e1c7d sp:7fff4a10d878 error:0 in chromium-browser". What I expect to happen: I haven't bothered to check how it should behave, but at least it shouldn't crash. Additional information: Seems to happen with both chromium-codecs-ffmpeg and chromium-codecs-ffmpeg-extra (from Medibuntu) alike. I'm attaching a backtrace. I did my best with it, but I'll readily admit I have no idea of its value. Please do advise me if I more -dbg packages or something else is needed. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 18.0.1025.168~r134367-0ubuntu0.12.04.1 Uname: Linux 3.3.3-030303-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CheckboxSubmission: 09ae689090491ca53449589269e4bfd8 CheckboxSystem: edda5d4f616ca792bf437989cb597002 ChromiumPrefs: can't open profile /home/jani/.config/chromium/Default/Preferences Date: Mon May 21 17:30:49 2012 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) SourcePackage: chromium-browser UpgradeStatus: Upgraded to precise on 2011-11-21 (182 days ago) chromium-default: CHROMIUM_FLAGS="" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1002325/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1219844] Re: eclipse crashes in Oxygen::MenuStateData::menuItemIsActive(_GtkWidget*) const
Could you report this at bugs.kde.org? I currently don't have much time to look into this, and other oxygen-gtk developers don't even know about this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1219844 Title: eclipse crashes in Oxygen::MenuStateData::menuItemIsActive(_GtkWidget*) const Status in “gtk2-engines-oxygen” package in Ubuntu: New Bug description: using eclipse kepler 64bit with oracle jvm and subclipse integration (javahl): 1) show history of a file 2) mark 2 revisions 3) context-menu: compare eclipse very often crashes with: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f8cee6e616c, pid=19673, tid=140244722247424 # # JRE version: 7.0_21-b11 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [liboxygen-gtk.so+0x7416c] Oxygen::MenuStateData::menuItemIsActive(_GtkWidget*) const+0x1c # # Core dump written. Default location: /home/juergen/core or core.19673 # # An error report file with more information is saved as: # /home/juergen/hs_err_pid19673.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gtk2-engines-oxygen 1.3.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Mon Sep 2 15:57:19 2013 InstallationDate: Installed on 2010-11-24 (1013 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MarkForUpload: True SourcePackage: gtk2-engines-oxygen UpgradeStatus: Upgraded to saucy on 2013-08-29 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/1219844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1142213]
> Ruslan ? oppinion ? Well, I'd in fact rather use "#define popen _popen" etc. on Windows (if this is what you mean by portability), not return to glib-specific code. popen() is much less likely to fail, and this is why I'd prefer using it instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs23 in Ubuntu. https://bugs.launchpad.net/bugs/1142213 Title: emacs23/24 and other GTK applications do not start when run in Kubuntu 13.04 with oxygen-gtk theme enabled Status in easytag: New Status in GNU Emacs: Confirmed Status in “emacs23” package in Ubuntu: Confirmed Status in “emacs24” package in Ubuntu: Confirmed Status in “oxygen-gtk3” package in Ubuntu: In Progress Status in “emacs23” source package in Raring: Fix Committed Status in “emacs24” source package in Raring: Fix Committed Status in “oxygen-gtk3” source package in Raring: Fix Released Status in “gtk2-engines-oxygen” package in Debian: Fix Released Bug description: [Impact] * Emacs24 does not startup in KDE [Test Case] * Install emacs24 * Set gtk3 theme to oxygen-gtk via systemsettings > Application Appearence > GTK * Run emacs24 * Install update * Try and run emacs24 again [Regression Potential] * Minimal * Upstream release for oxygen-gtk3 is only a bug fix release If I try to run emacs23 in Kubuntu 13.04, (KDE 4.10.0) I am finding that the GUI starts only some of the time. If the GUI doesn't start then I will only see a process running in htop or similar. Starting emacs in a terminal window with the -nw argument or installing the Lucid interface shows that emacs does run each time it starts so the problem is either with the emacs GTK interface or the GTK libraries. Emacs24 exhibits the same problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: emacs23 (not installed) ProcVersionSignature: Ubuntu 3.8.0-9.18-generic 3.8.1 Uname: Linux 3.8.0-9-generic x86_64 ApportVersion: 2.9-0ubuntu2 Architecture: amd64 Date: Sun Mar 3 14:19:01 2013 InstallationDate: Installed on 2013-01-05 (57 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130104) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=screen-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: emacs23 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/easytag/+bug/1142213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1142213]
> if we want to be extra sure, add a minimal requirement on the glib version > in our (master) CMakefiles. No, that's bad. This way you'll disable any older distros from being able to use latest oxygen-gtk release. I'd suggest that we leave both variants - via popen() and g_spawn...() - and use popen() only for that glib version(s) which fails (and warn user in cmake output that current glib version is bad). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs23 in Ubuntu. https://bugs.launchpad.net/bugs/1142213 Title: emacs23/24 and other GTK applications do not start when run in Kubuntu 13.04 with oxygen-gtk theme enabled Status in easytag: New Status in GNU Emacs: Confirmed Status in “emacs23” package in Ubuntu: Confirmed Status in “emacs24” package in Ubuntu: Confirmed Status in “oxygen-gtk3” package in Ubuntu: In Progress Status in “emacs23” source package in Raring: Fix Committed Status in “emacs24” source package in Raring: Fix Committed Status in “oxygen-gtk3” source package in Raring: Fix Released Status in “gtk2-engines-oxygen” package in Debian: Fix Released Bug description: [Impact] * Emacs24 does not startup in KDE [Test Case] * Install emacs24 * Set gtk3 theme to oxygen-gtk via systemsettings > Application Appearence > GTK * Run emacs24 * Install update * Try and run emacs24 again [Regression Potential] * Minimal * Upstream release for oxygen-gtk3 is only a bug fix release If I try to run emacs23 in Kubuntu 13.04, (KDE 4.10.0) I am finding that the GUI starts only some of the time. If the GUI doesn't start then I will only see a process running in htop or similar. Starting emacs in a terminal window with the -nw argument or installing the Lucid interface shows that emacs does run each time it starts so the problem is either with the emacs GTK interface or the GTK libraries. Emacs24 exhibits the same problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: emacs23 (not installed) ProcVersionSignature: Ubuntu 3.8.0-9.18-generic 3.8.1 Uname: Linux 3.8.0-9-generic x86_64 ApportVersion: 2.9-0ubuntu2 Architecture: amd64 Date: Sun Mar 3 14:19:01 2013 InstallationDate: Installed on 2013-01-05 (57 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130104) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=screen-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: emacs23 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/easytag/+bug/1142213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1142213]
> - it is defined on windows (with mingw at least) and works, but opens a > terminal to execute a command. (not so nice). And I'm not sure _popen would > fix this, would it ? Most likely it won't. But we can make something like this: #ifdef _WIN32 ShowWindow(GetConsoleWindow(),SW_HIDE); #endif before running popen(). (Ugly, but should do the trick.) > - on unix, it does not allow to easily redirect stderr, so you get an error > message (for every application) when kde4-config is not installed. So that I > had to add a 2> /dev/null (committed), to hide the (armless) error message, > in current master, because users were already complaining. This is more serious. Not sure how to fix this well enough... > popen being more likely to work on windows depends on MinGW (not even sure if > it is implemented with VC ...). _popen() is listed in MSDN, so this one should be available with VC. > So bottomline: if we want to stick to popen (to be more glib-error safe), > we'd likely need more code (and more #ifdef) than what we have now ... Yeah, hard to decide. Seems you're right and we should go back to glib. (But we should make sure this doesn't break any distro again if they still use unfixed glib version). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs23 in Ubuntu. https://bugs.launchpad.net/bugs/1142213 Title: emacs23/24 and other GTK applications do not start when run in Kubuntu 13.04 with oxygen-gtk theme enabled Status in easytag: New Status in GNU Emacs: Confirmed Status in “emacs23” package in Ubuntu: Confirmed Status in “emacs24” package in Ubuntu: Confirmed Status in “oxygen-gtk3” package in Ubuntu: In Progress Status in “emacs23” source package in Raring: Fix Committed Status in “emacs24” source package in Raring: Fix Committed Status in “oxygen-gtk3” source package in Raring: Fix Released Status in “gtk2-engines-oxygen” package in Debian: Fix Released Bug description: [Impact] * Emacs24 does not startup in KDE [Test Case] * Install emacs24 * Set gtk3 theme to oxygen-gtk via systemsettings > Application Appearence > GTK * Run emacs24 * Install update * Try and run emacs24 again [Regression Potential] * Minimal * Upstream release for oxygen-gtk3 is only a bug fix release If I try to run emacs23 in Kubuntu 13.04, (KDE 4.10.0) I am finding that the GUI starts only some of the time. If the GUI doesn't start then I will only see a process running in htop or similar. Starting emacs in a terminal window with the -nw argument or installing the Lucid interface shows that emacs does run each time it starts so the problem is either with the emacs GTK interface or the GTK libraries. Emacs24 exhibits the same problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: emacs23 (not installed) ProcVersionSignature: Ubuntu 3.8.0-9.18-generic 3.8.1 Uname: Linux 3.8.0-9-generic x86_64 ApportVersion: 2.9-0ubuntu2 Architecture: amd64 Date: Sun Mar 3 14:19:01 2013 InstallationDate: Installed on 2013-01-05 (57 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130104) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=screen-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: emacs23 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/easytag/+bug/1142213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 963736] Re: thunderbird and firefox freeze at random : must be killed and restarted
@Rohan 5e22bbf8bf09663f2be9cd7510a956fc5ad4faba is the core of the fix. The two follow-up patches are minor improvements on it. They are not required to have this work. Also, if all goes as planned, oxygen-gtk{2,3} with this fix is expected to be released today. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/963736 Title: thunderbird and firefox freeze at random : must be killed and restarted Status in “gtk2-engines-oxygen” package in Ubuntu: Fix Committed Status in “gtk2-engines-oxygen” source package in Raring: Fix Committed Status in “gtk2-engines-oxygen” source package in Saucy: Fix Committed Bug description: [Impact] Thunderbird freezes at random. I must kill it then reload it. Sometimes the freeze happens when sending a mail. I had no problem in 11.10. It happens several times a day. The only pattern that I can currently see is that the freeze happens frequently when thunderbird is using the network. [Test Case] * Install update * Run Firefox/Thunderbird for a day * Make sure it does not freeze [Regression Potential] * Minimal * Upstream release for gtk2-engines-oxygen is only a bug fix release $ lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 $ dpkg-query -s thunderbird Package: thunderbird Status: install ok installed Priority: optional Section: mail Installed-Size: 45256 Maintainer: Ubuntu Mozilla Team Architecture: amd64 Version: 11.0+build1-0ubuntu1 [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/963736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 963736] Re: thunderbird and firefox freeze at random : must be killed and restarted
Unfortunately, the fixes are not yet released. They can be accessed in latest git oxygen-gtk. For the record, here're the relevant commits: http://commits.kde.org/oxygen-gtk/51b662b0cd86fd7a960cc2f0c436441d64b2dd44 for oxygen-gtk3 http://commits.kde.org/oxygen-gtk/a515ab451f54cbc930d0a09d250669255dd8a741 for oxygen-gtk2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/963736 Title: thunderbird and firefox freeze at random : must be killed and restarted Status in “gtk2-engines-oxygen” package in Ubuntu: Confirmed Status in “thunderbird” package in Ubuntu: Confirmed Bug description: Thunderbird freezes at random. I must kill it then reload it. Sometimes the freeze happens when sending a mail. I had no problem in 11.10. It happens several times a day. The only pattern that I can currently see is that the freeze happens frequently when thunderbird is using the network. $ lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 $ dpkg-query -s thunderbird Package: thunderbird Status: install ok installed Priority: optional Section: mail Installed-Size: 45256 Maintainer: Ubuntu Mozilla Team Architecture: amd64 Version: 11.0+build1-0ubuntu1 [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/963736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1142213] Re: emacs23/24 GUI does not start when run in Kubuntu 13.04 with oxygen-gtk theme enabled
See also https://bugs.kde.org/show_bug.cgi?id=318891 . We've worked around this bug in oxygen-gtk, commits are in current git. ** Bug watch added: KDE Bug Tracking System #318891 https://bugs.kde.org/show_bug.cgi?id=318891 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines-oxygen in Ubuntu. https://bugs.launchpad.net/bugs/1142213 Title: emacs23/24 GUI does not start when run in Kubuntu 13.04 with oxygen- gtk theme enabled Status in “emacs23” package in Ubuntu: Confirmed Status in “emacs24” package in Ubuntu: Confirmed Status in “gtk2-engines-oxygen” package in Ubuntu: Confirmed Status in “oxygen-gtk3” package in Ubuntu: Confirmed Bug description: If I try to run emacs23 in Kubuntu 13.04, (KDE 4.10.0) I am finding that the GUI starts only some of the time. If the GUI doesn't start then I will only see a process running in htop or similar. Starting emacs in a terminal window with the -nw argument or installing the Lucid interface shows that emacs does run each time it starts so the problem is either with the emacs GTK interface or the GTK libraries. Emacs24 exhibits the same problem. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: emacs23 (not installed) ProcVersionSignature: Ubuntu 3.8.0-9.18-generic 3.8.1 Uname: Linux 3.8.0-9-generic x86_64 ApportVersion: 2.9-0ubuntu2 Architecture: amd64 Date: Sun Mar 3 14:19:01 2013 InstallationDate: Installed on 2013-01-05 (57 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130104) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=screen-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: emacs23 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/1142213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1152335] [NEW] NetworkManager doesn't connect to Mobile Broadband
Public bug reported: I have an HSDPA USB Stick modem model E1550, detected by lsusb as follows: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem. I add a new Mobile Broadband connection in KDE Network Manager Settings, it correctly finds the modem and allows me to select my country and operator (Russia Beeline). I select default APN, which is home.beeline.ru (though I've also tried internet.beeline.ru as is told on their website), then say Finish. Dial number, username and password are correctly detected. I select PIN as "Not required". Now I press OK in the dialog appeared, and try connecting from plasma network-manager widget, and... nothing happens. Seemingly. I get this output in /var/log/syslog: ___cut_here___ Mar 8 01:28:51 integral1 NetworkManager[9077]: Activation (ttyUSB0) starting connection 'Beeline - 3G modem' Mar 8 01:28:51 integral1 NetworkManager[9077]: (ttyUSB0): device state change: disconnected -> prepare (reason 'none') [30 40 0] Mar 8 01:28:51 integral1 NetworkManager[9077]: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Mar 8 01:28:51 integral1 NetworkManager[9077]: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Mar 8 01:28:51 integral1 NetworkManager[9077]: (ttyUSB0): device state change: prepare -> need-auth (reason 'none') [40 60 0] Mar 8 01:28:51 integral1 NetworkManager[9077]: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Mar 8 01:28:51 integral1 modem-manager[9075]: Modem /org/freedesktop/ModemManager/Modems/5: state changed (connected -> disconnecting) Mar 8 01:28:51 integral1 modem-manager[9075]: Modem /org/freedesktop/ModemManager/Modems/5: state changed (disconnecting -> connected) Mar 8 01:28:51 integral1 NetworkManager[9077]: disconnect failed: (32) The serial port is not open. Mar 8 01:28:51 integral1 NetworkManager[9077]: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled... Mar 8 01:28:51 integral1 NetworkManager[9077]: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started... Mar 8 01:28:51 integral1 NetworkManager[9077]: (ttyUSB0): device state change: need-auth -> prepare (reason 'none') [60 40 0] Mar 8 01:28:51 integral1 NetworkManager[9077]: Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete. Mar 8 01:28:51 integral1 NetworkManager[9077]: GSM connection failed: (32) Sending command failed: device is not enabled Mar 8 01:28:51 integral1 NetworkManager[9077]: (ttyUSB0): device state change: prepare -> failed (reason 'unknown') [40 120 1] Mar 8 01:28:51 integral1 modem-manager[9075]: Modem /org/freedesktop/ModemManager/Modems/5: state changed (connected -> disconnecting) Mar 8 01:28:51 integral1 modem-manager[9075]: Modem /org/freedesktop/ModemManager/Modems/5: state changed (disconnecting -> connected) Mar 8 01:28:51 integral1 NetworkManager[9077]: Activation (ttyUSB0) failed. Mar 8 01:28:51 integral1 NetworkManager[9077]: disconnect failed: (32) The serial port is not open. Mar 8 01:28:51 integral1 NetworkManager[9077]: (ttyUSB0): device state change: failed -> disconnected (reason 'none') [120 30 0] Mar 8 01:28:51 integral1 NetworkManager[9077]: (ttyUSB0): deactivating device (reason 'none') [0] Mar 8 01:28:51 integral1 NetworkManager[9077]: nm_system_iface_flush_routes: assertion `ifindex > 0' failed Mar 8 01:28:51 integral1 NetworkManager[9077]: nm_system_iface_flush_addresses: assertion `ifindex > 0' failed ___cut_here___ I've tried changing various settings, but NetworkManager didn't manage to connect. OK, I've gone another way: using wvdial. Here's config which I used: ___cut_here___ [Dialer Defaults] Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Modem Type = Analog Modem Phone = *99# ISDN = 0 Username = beeline Init1 = ATZ Password = beeline Modem = /dev/ttyUSB0 Baud = 9600 Stupid mode = 1 ___cut_here___ And, it worked! So, basically NetworkManager was unable to connect while wvdial connected almost immediately. Notice that maybe the fact that I didn't have to enter APN might have done the thing, but I don't know how that should be done in NetworkManager. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1152335 Title: NetworkManager doesn't connect to Mobile Broadband Status in “network-manager” package in Ubuntu: New Bug description: I have an HSDPA USB Stick modem model E1550, detected by lsusb as follows: ID 12d1:1001 Huawei Technologies Co., Ltd. E169/E620/E800 HSDPA Modem. I a
[Desktop-packages] [Bug 1130869] Re: jockey-kde crashes on startup in QWidgetPrivate::deleteTLSysExtra
Argh... seems DrKonqi didn't attach backtrace etc Here it is ** Attachment added: "DrKonqi's report" https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1130869/+attachment/3538865/+files/python2-20130220-235640.kcrash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1130869 Title: jockey-kde crashes on startup in QWidgetPrivate::deleteTLSysExtra Status in “jockey” package in Ubuntu: New Bug description: I started jockey-kde and it immediately crashed with sigsegv. Here's console output from it if it may be helpful: ruslan@ocz-atv-u1204:~$ jockey-kde ERROR:root:Could not find any typelib for AppIndicator3 Traceback (most recent call last): File "/usr/bin/jockey-kde", line 472, in sys.exit(u.run()) File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 468, in run self.ui_show_main() File "/usr/bin/jockey-kde", line 159, in ui_show_main self.update_tree_model() File "/usr/bin/jockey-kde", line 315, in update_tree_model self.mw.label_heading.setText('%s%s' % self.main_window_text()) File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 223, in main_window_text info = self.backend().handler_info(h_id) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Python.ValueError: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 707, in _message_cb retval = candidate_method(self, *args, **keywords) File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 264, in handler_info 'recommended': str(h.recommended()), File "/usr/share/jockey/handlers/nvidia.py", line 130, in recommended nd = NvidiaDetection() File "/usr/lib/python2.7/dist-packages/NvidiaDetector/nvidiadetector.py", line 68, in __init__ self.getData() File "/usr/lib/python2.7/dist-packages/NvidiaDetector/nvidiadetector.py", line 149, in getData driver_version = self.__get_value_from_name(stripped_package_name) File "/usr/lib/python2.7/dist-packages/NvidiaDetector/nvidiadetector.py", line 87, in __get_value_from_name v = int(name) ValueError: invalid literal for int() with base 10: 'experimental-304' KCrash: Application '' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/ruslan/.kde/socket-ocz-atv-u1204/kdeinit4__0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1130869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1130869] [NEW] jockey-kde crashes on startup in QWidgetPrivate::deleteTLSysExtra
Public bug reported: I started jockey-kde and it immediately crashed with sigsegv. Here's console output from it if it may be helpful: ruslan@ocz-atv-u1204:~$ jockey-kde ERROR:root:Could not find any typelib for AppIndicator3 Traceback (most recent call last): File "/usr/bin/jockey-kde", line 472, in sys.exit(u.run()) File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 468, in run self.ui_show_main() File "/usr/bin/jockey-kde", line 159, in ui_show_main self.update_tree_model() File "/usr/bin/jockey-kde", line 315, in update_tree_model self.mw.label_heading.setText('%s%s' % self.main_window_text()) File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 223, in main_window_text info = self.backend().handler_info(h_id) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Python.ValueError: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 707, in _message_cb retval = candidate_method(self, *args, **keywords) File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 264, in handler_info 'recommended': str(h.recommended()), File "/usr/share/jockey/handlers/nvidia.py", line 130, in recommended nd = NvidiaDetection() File "/usr/lib/python2.7/dist-packages/NvidiaDetector/nvidiadetector.py", line 68, in __init__ self.getData() File "/usr/lib/python2.7/dist-packages/NvidiaDetector/nvidiadetector.py", line 149, in getData driver_version = self.__get_value_from_name(stripped_package_name) File "/usr/lib/python2.7/dist-packages/NvidiaDetector/nvidiadetector.py", line 87, in __get_value_from_name v = int(name) ValueError: invalid literal for int() with base 10: 'experimental-304' KCrash: Application '' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/ruslan/.kde/socket-ocz-atv-u1204/kdeinit4__0 ** Affects: jockey (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1130869 Title: jockey-kde crashes on startup in QWidgetPrivate::deleteTLSysExtra Status in “jockey” package in Ubuntu: New Bug description: I started jockey-kde and it immediately crashed with sigsegv. Here's console output from it if it may be helpful: ruslan@ocz-atv-u1204:~$ jockey-kde ERROR:root:Could not find any typelib for AppIndicator3 Traceback (most recent call last): File "/usr/bin/jockey-kde", line 472, in sys.exit(u.run()) File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 468, in run self.ui_show_main() File "/usr/bin/jockey-kde", line 159, in ui_show_main self.update_tree_model() File "/usr/bin/jockey-kde", line 315, in update_tree_model self.mw.label_heading.setText('%s%s' % self.main_window_text()) File "/usr/lib/python2.7/dist-packages/jockey/ui.py", line 223, in main_window_text info = self.backend().handler_info(h_id) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Python.ValueError: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 707, in _message_cb retval = candidate_method(self, *args, **keywords) File "/usr/lib/python2.7/dist-packages/jockey/backend.py", line 264, in handler_info 'recommended': str(h.recommended()), File "/usr/share/jockey/handlers/nvidia.py", line 130, in recommended nd = NvidiaDetection() File "/usr/lib/python2.7/dist-packages/NvidiaDetector/nvidiadetector.py", line 68, in __init__ self.getData() File "/usr/lib/python2.7/dist-packages/NvidiaDetector/nvidiadetector.py", line 149, in getData driver_version = self.__get_value_from_name(stripped_package_name) File "/usr/lib/python2.7/dist-packages/NvidiaDetector/nvidiadetector.py", line 87, in __get_value_from_name v = int(name) ValueError: invalid literal for int() with base 10: 'experimental-304' KCrash: Application '' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit sock_file=/home/ruslan/.kde/socket-ocz-atv-u1204/kdeinit4__0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1130869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 918791] Re: qemu-kvm dies when using vmvga driver and unity in the guest
I've checked Serge's fix and it does fix crashes. Now I've pulled latest qemu-kvm git master, and it appears that this patch isn't there... I still have to apply it on top of latest git to avoid crashes. What progress is here? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/918791 Title: qemu-kvm dies when using vmvga driver and unity in the guest Status in QEMU: New Status in “qemu-kvm” package in Ubuntu: Fix Released Status in “xserver-xorg-video-vmware” package in Ubuntu: Invalid Status in “qemu-kvm” source package in Oneiric: Fix Committed Status in “xserver-xorg-video-vmware” source package in Oneiric: Invalid Status in “qemu-kvm” source package in Precise: Fix Released Status in “xserver-xorg-video-vmware” source package in Precise: Invalid Bug description: = SRU Justification: 1. impact: kvm crashes 2. Development fix: don't allow attempts to set_bit to negative offsets 3. Stable fix: same as development fix 4. Test case (see below) 5. Regression potential: if the patch is wrong, graphics for vmware vga over vnc could get messed up = 12.04's qemu-kvm has been unstable for me and Marc Deslauriers and I figured out it has something to do with the interaction of qemu-kvm, unity and the vmvga driver. This is a regression over qemu-kvm in 11.10. TEST CASE: 1. start a VM that uses unity (eg, 11.04, 11.10 or 12.04). My tests use unity-2d on an amd64 host and amd64 guests 2. on 11.04 and 11.10, open empathy via the messaging indicator and click 'Chat'. On 12.04, open empathy via the messaging indicator and click 'Chat', close the empathy wizard, move the empathy window over the unity luancher (so it autohides), then do 'ctrl+alt+t' to open a terminal When the launcher tries to auto(un)hide, qemu-kvm dies with this: [10574.958149] do_general_protection: 132 callbacks suppressed [10574.958154] kvm[13192] general protection ip:7fab9680ea0f sp:74440148 error:0 in qemu-system-x86_64[7fab966c4000+2c9000] Relevant libvirt xml: If I change to using 'cirrus', then qemu-kvm no longer crashes. Eg: The workaround is therefore to use the cirrus driver instead of vmvga, however being able to kill qemu-kvm in this manner is not ideal. Also, unfortunately unity-2d does not run with with cirrus driver under 11.04, so the security and SRU teams are unable to properly test updates in GUI applications under unity when using the current 12.04 qemu-kvm. I tried to report this via apport, but apport complained about a CRC error, so I could not. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/918791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1073659] [NEW] Long delay between print job creation and actual start of printing
Public bug reported: 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&interface=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 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise third-party-packages -- You received this bug notification because you are a member of Desktop 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: New 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&interface=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 S
[Desktop-packages] [Bug 412730] Re: Printer Applet infinite notification: Printer may not be connected
This is still present in Precise (at least Printer Applet spamming about "may not be connected" every second) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/412730 Title: Printer Applet infinite notification: Printer may not be connected Status in “cups” package in Ubuntu: Expired Bug description: Binary package hint: cups I am using Kubuntu9.04 with KDE 4.3 When I print from any application, I can choose from a long list of printers that happen to be connected to the same network, in the KDE print dialog. After printing to one of these auto-listed printers, the document was processing indefinitely, and worse, the Printer Applet keeps on notifying that the Printer '' may not be connected (see attached screenshot). The KDE Printer Applet is unresponsive, but I can delete the print job from the cups web interface. Even after deleting the print job the notifications persist. However, interestingly, when I try to get more information on this printer in the cups web interface, the link refers to a remote cups server. If i print with the same printer, but in stead a manually configured entry in cups, it works fine. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 MachineType: ASUSTeK Computer Inc. A8J NonfreeKernelModules: nvidia Package: cups 1.3.9-17ubuntu3.2 Papersize: letter PpdFiles: gc257: HP LaserJet 4250 Postscript (recommended) PDF: Generic PDF file generator pawprints: HP LaserJet 9000 Series Postscript (recommended) gc257-2: HP LaserJet 4250 Postscript (recommended) ProcCmdLine: root=UUID=fa7e9c2c-5ec4-4b92-aa31-6c05d486 ro quiet splash ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.28-14.47-generic SourcePackage: cups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/412730/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1001028] Re: Delay after every print job on USB
I have this problem with Epson Stylus Photo R300 printer, tried setting lpadmin -p Stylus-Photo-R330 -o usb-unidir-default=true but still have several seconds delay at the end of print job, i.e. the printer stops, waits several seconds, then does final carriage return and paper feed. I've also tried to restart cups (just in case), but it didn't help. I have the following in dmesg: [18990.523142] usblp0: removed # when print job starts [19019.917018] usblp0: USB Bidirectional printer dev 8 if 1 alt 0 proto 2 vid 0x04B8 pid 0x0803 # when printer finally does paper feed Do I understand correctly that this should have worked with current cups in Precise? Any help, please? ** Attachment added: "Printer lsusb output" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1001028/+attachment/3418957/+files/printer.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1001028 Title: Delay after every print job on USB Status in “cups” package in Ubuntu: Fix Released Status in “cups” source package in Precise: Fix Released Bug description: Ubuntu 12.04 64 bit (also 32 bit is affected) Zebra LP 2844-Z USB printer - connected with a generic "raw queue" driver. usblp0 appears to disconnect after every print job and then automatically reconnect after 8 seconds. The next job to the printer won't print until it is reconnected. This is a problem for us in a high volume printing scenario. Here are messages from syslog: May 17 16:47:17 mlcx500 kernel: [25464.991868] usblp0: removed May 17 16:47:25 mlcx500 kernel: [25473.131745] usblp0: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x0A5F pid 0x0027 May 17 16:47:25 mlcx500 udev-configure-printer: add /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/usb/lp0 May 17 16:47:25 mlcx500 udev-configure-printer: device devpath is /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2 May 17 16:47:25 mlcx500 udev-configure-printer: Device already handled Note the 8 second pause between the first and second messages. Not sure where the disconnect is coming from. It doesn't appear to be hardware related as I have the problem with various combinations of printer and computer. [IMPACT] On some printers it can happen that with Precise's new libusb-based USB CUPS backend there is a small delay of around 8 seconds after each job. In environments where printers are continuously printing small jobs (~1 page each) this is a serious impact on printing performance. The USB backend in the proposed package has a configurable option to turn off the bi-directional operation of the backend (sending print data and also reading answers of the printer). With uni-directional printing (only sending print data) the delay disappears. Uni-directional printing can be set manually. We will give instructions in the Release Notes of 12.04.1. [TESTCASE] Unfortunately, for reproducing this bug one needs the actual printer. Connect a printer with the problem to the USB port of the computer. With current Precise you get the mentioned 8-second delay after each job when you print several jobs one after the other. If you install the proposed package you can suppress bi-directional printing via lpadmin -p -o usb-unidir-default=true Now the jobs get printed directly one after the other. [Regression Potential] The patch looks perhaps more dramatic than it is. This is because several code sections are put into "if" blocks, indenting all the (unchanged) code lines. This especially happens because now we suppress using the back channel for selected printers (and also printers which claim to be uni-directional only). The code was developed in several steps and uploaded step-by-step to my PPA. There the reporters of the bugs covered by this SRU and some additional bugs (bug 902535, bug 995111) tested it intensively. They did not hit any regressions compared to stock Precise or the first CUPS SRU. The code is also applied to the CUPS package in Quantal and this also did not cause any regression bug report yet. I have tested the code on four HP printers (HP LaserJet 3390, HP Color LaserJet CM3530 MFP, HP PhotoSmart C8100, HP PhotoSmart C5200, all on direct USB) and one Epson printer (Epson Stylus Photo 880, both direct USB and parallel with Prolific USB -> Parallel adaptor) and all work fine, no regressions. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups 1.5.2-9ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Thu May 17 17:47:22 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) Lpstat: device for Officejet-6300-series: dnssd://Officejet%206300%20series%20%5B75F80
[Desktop-packages] [Bug 488247] Re: Inkscape is slow starting
Since the icons appear complex enough to take tens of seconds from startup I wonder why couldn't inkscape cache them to config dir on first start? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/488247 Title: Inkscape is slow starting Status in Inkscape: A Vector Drawing Tool: Triaged Status in “inkscape” package in Ubuntu: Triaged Status in “inkscape” package in Debian: Confirmed Status in Gentoo Linux: Unknown Status in “inkscape” package in Mandriva: Unknown Bug description: Hi, Although Inkscape is a nice program, I recognize that it's becoming slower and slower each time a new version is released. Also I have compiled inkscape from subversion (Revision: 22608) in a Ubuntu 8.10 box. (Intel Core 2 duo 1.8 GHz and 2 GB of RAM) In the build I have disabled the -g option in all the Makefiles, but launching inkscape takes more than 10 seconds!! And in its actions it demostrates that it has become slower. Is any way to improve the performance of Inkscape (for example, using a separate thread to loading the plugins, using a load of components by demand, using OpenGL+Shaders for drawings,...) I have some knowledge of optimization in C/C++ but I know next to nothing how Inkscape has been programmed. Thanks guys for this great program. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/488247/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 488247] Re: Inkscape is slow starting
Just tried profiling inkscape after main window has showed and maximized. It feels unresponsive about first 20 seconds, e.g. cursor position indicators in the rulers are jumpy instead of smoothly following the cursor. ** Attachment added: "Profile of first ~20 seconds after startup" https://bugs.launchpad.net/inkscape/+bug/488247/+attachment/3332724/+files/inkscape-after-startup-profile.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/488247 Title: Inkscape is slow starting Status in Inkscape: A Vector Drawing Tool: Triaged Status in “inkscape” package in Ubuntu: Triaged Status in “inkscape” package in Debian: Confirmed Status in Gentoo Linux: Unknown Status in “inkscape” package in Mandriva: Unknown Bug description: Hi, Although Inkscape is a nice program, I recognize that it's becoming slower and slower each time a new version is released. Also I have compiled inkscape from subversion (Revision: 22608) in a Ubuntu 8.10 box. (Intel Core 2 duo 1.8 GHz and 2 GB of RAM) In the build I have disabled the -g option in all the Makefiles, but launching inkscape takes more than 10 seconds!! And in its actions it demostrates that it has become slower. Is any way to improve the performance of Inkscape (for example, using a separate thread to loading the plugins, using a load of components by demand, using OpenGL+Shaders for drawings,...) I have some knowledge of optimization in C/C++ but I know next to nothing how Inkscape has been programmed. Thanks guys for this great program. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/488247/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 488247] Re: Inkscape is slow starting
Inkscape 0.48.3.1 r9886, starting very slow. Here's sysprof profile of startup. Seems too much time is spent in prerender_icon(). ** Attachment added: "Startup sysprof profile" https://bugs.launchpad.net/inkscape/+bug/488247/+attachment/3332723/+files/inkscape-startup-profile.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/488247 Title: Inkscape is slow starting Status in Inkscape: A Vector Drawing Tool: Triaged Status in “inkscape” package in Ubuntu: Triaged Status in “inkscape” package in Debian: Confirmed Status in Gentoo Linux: Unknown Status in “inkscape” package in Mandriva: Unknown Bug description: Hi, Although Inkscape is a nice program, I recognize that it's becoming slower and slower each time a new version is released. Also I have compiled inkscape from subversion (Revision: 22608) in a Ubuntu 8.10 box. (Intel Core 2 duo 1.8 GHz and 2 GB of RAM) In the build I have disabled the -g option in all the Makefiles, but launching inkscape takes more than 10 seconds!! And in its actions it demostrates that it has become slower. Is any way to improve the performance of Inkscape (for example, using a separate thread to loading the plugins, using a load of components by demand, using OpenGL+Shaders for drawings,...) I have some knowledge of optimization in C/C++ but I know next to nothing how Inkscape has been programmed. Thanks guys for this great program. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/488247/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 794771] Re: metacity doesn't start, dies with "metacity:ERROR:ui/ui.c:754:meta_ui_get_default_window_icon: assertion failed: (default_icon)"
This bug is still present in 10.04 LTS. Since it's LTS, it seems the fix released should be backported to Lucid, or am I wrong? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/794771 Title: metacity doesn't start, dies with "metacity:ERROR:ui/ui.c:754:meta_ui_get_default_window_icon: assertion failed: (default_icon)" Status in “metacity” package in Ubuntu: Fix Released Bug description: Binary package hint: metacity strace attached ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: metacity 1:2.34.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.39-3.10-generic-pae 2.6.39 Uname: Linux 2.6.39-3-generic-pae i686 Architecture: i386 Date: Thu Jun 9 00:31:46 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928.1) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: metacity UpgradeStatus: Upgraded to oneiric on 2011-04-20 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/794771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 744580] Re: Firefox doesn't auto scroll when selecting content downwards
Confirm this bug on ubuntu11.10(gnome-shell or unity). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/744580 Title: Firefox doesn't auto scroll when selecting content downwards Status in The Mozilla Firefox Browser: Confirmed Status in “firefox” package in Ubuntu: Fix Released Status in “firefox” source package in Natty: Fix Released Bug description: Binary package hint: firefox Open firefox 4 Go full screen Open a long page such as this one:- http://mail.gnome.org/archives/commits-list/2011-March/msg03805.html Try to highlight a large chunk of text starting on screen and move the mouse down and try to go off the bottom of the screen (selecting text). Note that the browser doesn't scroll down. This is the bug. Note that if you scroll the window to the bottom and drag upwards it does scroll upwards as you select. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 4.0~rc2+build3+nobinonly-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Mar 28 22:25:33 2011 FirefoxPackages: firefox 4.0~rc2+build3+nobinonly-0ubuntu1 flashplugin-installer N/A adobe-flashplugin N/A icedtea-plugin 1.1~20110320-0ubuntu1 InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: Upgraded to natty on 2011-01-19 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/744580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp