[Desktop-packages] [Bug 1885344] [NEW] nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build
Public bug reported: Nvidia kernel module fails to build with linux kernel 5.6.0. Exits with error code 2. Description:Ubuntu 20.04 LTS Release:20.04 linux-image-unsigned-5.6.0-1018-oem: Installed: 5.6.0-1018.18 Candidate: 5.6.0-1018.18 Version table: *** 5.6.0-1018.18 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.6.0-1018-oem Date: Sat Jun 27 02:15:51 2020 DuplicateSignature: dkms:nvidia-340:340.108-0ubuntu2:/var/lib/dkms/nvidia-340/340.108/build/nv-drm.c:54:25: error: implicit declaration of function ‘drm_pci_init’; did you mean ‘drm_mm_init’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-04-24 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu2 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1885344 Title: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Nvidia kernel module fails to build with linux kernel 5.6.0. Exits with error code 2. Description: Ubuntu 20.04 LTS Release: 20.04 linux-image-unsigned-5.6.0-1018-oem: Installed: 5.6.0-1018.18 Candidate: 5.6.0-1018.18 Version table: *** 5.6.0-1018.18 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.6.0-1018-oem Date: Sat Jun 27 02:15:51 2020 DuplicateSignature: dkms:nvidia-340:340.108-0ubuntu2:/var/lib/dkms/nvidia-340/340.108/build/nv-drm.c:54:25: error: implicit declaration of function ‘drm_pci_init’; did you mean ‘drm_mm_init’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-04-24 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 340.108-0ubuntu2 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1885344/+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 1555485] [NEW] WebGL not working with the latest Firefox version
Public bug reported: The WebGL stooped working with the latest version of firefox. Ubuntu 14.04.4 LTS 64bit firefox 45.0+build2-0ubuntu0.14.04.1 using NVidia driver 340.96 Graphic card - GeForce GT 240 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1555485 Title: WebGL not working with the latest Firefox version Status in firefox package in Ubuntu: New Bug description: The WebGL stooped working with the latest version of firefox. Ubuntu 14.04.4 LTS 64bit firefox 45.0+build2-0ubuntu0.14.04.1 using NVidia driver 340.96 Graphic card - GeForce GT 240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1555485/+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 517021] Re: gvfsd-metadata causes 100% CPU usage
I've installed gvfs 1.20.3-0ubuntu1.1 and other gvfs* packages with the same version that come with it from trusty-proposde under Trusty (Ubuntu 14.04) on both my PC and laptop and so far (second day of using it) I haven't been hit by this bug. -- 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/517021 Title: gvfsd-metadata causes 100% CPU usage Status in GVFS: Unknown Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Precise: Fix Committed Status in gvfs source package in Trusty: Fix Committed Status in gvfs source package in Utopic: Fix Committed Status in gvfs source package in Vivid: Fix Released Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using "top" i can see that "gvfsd-metadata" is using 100% CPU and when i kill it the computer stops "hanging". I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+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 517021] Re: gvfsd-metadata causes 100% CPU usage
Also, I don;t think that the current incarnation of this bug is filling my HDD. When I open the ~/.local/share/gvfs-metadata folder in the file browser it is evident that a few files are constantly being generated and then erased ad nauseam. So there is no disk space eating problem, just the HDD (and laptop battery) straining problem. -- 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/517021 Title: gvfsd-metadata causes 100% CPU usage Status in gvfs package in Ubuntu: Confirmed Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using "top" i can see that "gvfsd-metadata" is using 100% CPU and when i kill it the computer stops "hanging". I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+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 517021] Re: gvfsd-metadata causes 100% CPU usage
I would like to add that I don't think that the original bug reported with this bug report, is identical with the way this gvfs-metadata bug behaves in its later version as running rm -rf ~/.local/share/gvfs- metadata stops the infinite disk writing for just few minutes and that it starts again. Not only does it put the HDD under a strain (especially SSDs), it also kills the battery on laptop devices quicker especially when an ordinary HDD is used. The finding that the bug is easily reproducible with the Super Start firefox extension is interesting. I'm using a similar extension on both my machines where this bug appears; it's Speed DIal [FWD] in my case. Some previous bug reports mention that the bug is triggered when using HTML5 Video Everywhere - another firefox plugin. Is it possible that some of the libraries used by firefox produce files (or do something else) that than somehow confuse gvfs-metadata and force it to go into infinite writing loop?! If so, can this be also a firefox bug? Not that gvfs-metadata shouldn't be able to handle such situations. -- 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/517021 Title: gvfsd-metadata causes 100% CPU usage Status in gvfs package in Ubuntu: Confirmed Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using "top" i can see that "gvfsd-metadata" is using 100% CPU and when i kill it the computer stops "hanging". I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+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 517021] Re: gvfsd-metadata causes 100% CPU usage
John Paul Adrian Glaubitz (glaubitz) what use do I have that this bug might have been fixed around gvfs_1.22 when the Ubuntu 14.04.1 that I currently use uses gvfs (1.20.3-0ubuntu1) released 2015-02-02 and this bug is still present in it?! For those that need a temporary fix for this bug, use the sudo chmod -x /usr/lib/gvfs/gvfsd-metadata (makes gvfs-metadata non executable) command, but be warned, after doing this nautilus tends to forget some settings and tweaks. For instance, on my computer, the desktop icons ( I have "show desktop icons" enabled) tend to be moved on the left side of the screen (in random order) on each system restart (this will definitely happen if you erased the file(s) in ~/.local/share/gvfs- metadata). The "fix" can be reversed with sudo chmod +x /usr/lib/gvfs/gvfsd-metadata (makes gvfs-metadata executable again). -- 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/517021 Title: gvfsd-metadata causes 100% CPU usage Status in gvfs package in Ubuntu: Confirmed Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs My disk space was really full at one moment, no byte left free. People say, that does corrupt the files in the ~/.local/share/gvfs-metadata folder, so the gvfsd-metadata can't read it without being screwed up. Workaround: run "rm -rf ~/.local/share/gvfs-metadata" Expected results: gvfsd-metadata should be able to handle the no space left situation. --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using "top" i can see that "gvfsd-metadata" is using 100% CPU and when i kill it the computer stops "hanging". I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+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 1272613] Re: evince-thumbnailer crashed with SIGSEGV
Any news on fixing this bug? Can someone guide me with step by step instructions to generating crash report files for this bug as I'm hit by it in the most dreadful way. Browsing my directories containing pdf files (actually pdf books) crashes my computer, resulting in a blank screen, a blinking led light indicationg hard disk activity after which all I can do is press the reset button and restart the computer. I've been hit by this bug for the first time almost a year ago when I was still using Ubuntu 12.04. At that time the crashes were so bad that i couldn;t even start the computer unless I unplugged the electrical cord since the computer simply refused to boot up again after pressing the power button to turn it off and then pressing the power button to turn it on again. At that time I was convinced that it might have something to do with: a) a failing harddrive b) a failing power supply c) a failing motherboard I assumed option a) because I have multiple HD-s installed into my computer. I use one of them specifically for storing ebooks (most of them in pdf format). But then i realised that this crashes appear even during a generation of pdf thumbnails on my main HD - the one that has the operating system and my home directory on that at the time I started having this problem was only a month old. Also I was getting kernel messages about disk i/o errors labeled with date/time that coincided with the crashes. Since I have 4 HD-s in my system and the crashes happened during pdf thumbnail generation for files on each of them, I ruled out this assumption about a failing HD. Then I moved on to analyzing assumption b). I presume that having installed 4HD's in a system with an older power supply that was already built in the computer case that I bought at the time I bought the parts for my computer(which equals to a very cheap and mediocre power supply) could be the reason for the crashes. Since the crashes came soon after I installed yet another HD (a fourth one) it sounded reasonable that maybe the weak power supply is the culprit for the crashes. After making multiple tweaks with the HD cables (changind the PATA ports) etc and temporarily disconnection some of the disk I finally decided to purchase a better power supply since I was a bit desperate and since it would have been a cheaper purchase than buying a new motherboard. This didn't work either. Then while looking for a new motherboard to buy - this is a core2duo system and motherboards compatible with my processor and My DDR2 memory are no longer easy to find I suddenly remembered that I added some pdf related PPA to my system at the time that i started experiencing the crashes. This was almost 3-4 months after I started having the crashes. I uninstalled the PPA and suddenly the system crashes disappeared. Although I still find it unbelievable that a user space program can bring the system to its knees, it seams that this was the exact case!!! After this I decided to be more careful with adding untrusted PPAs. I even got the impression that the PPA package was even tampered with due to the believe in the "mighty uncrushable linux". All worked fine on my Ubuntu 12.04.5 system until few days ago I finally decided it is time to do the upgrade to 14.04. Yesterday few days after the upgrade, I needed to look for some of the pdf books stored on my other drive. Since I wiped the thumbnail directory from my home drive after the clean installation of Ubuntu 14.04.1 (I have separate / and home partitions) nautilus has to recreate the pdf thumbnails. As I said most of my pdf files are stored on a separate HD. Most of them are e-books stored in multiple directories named by a subject. Some of the directories contain 4 pdf files, some 20, some 100+. Opening some of the directories containing pdf files work. All of the pdf thumbnails are being normally generated. But certain directories are "dangerous" to be opened. The thumbnailer manages to generate a few thumbnails and then my whole system crashes. Sometimes opening the same directory after the crash works. The thumbnailer manages to generate the rest of the thumbnails. Just before I sat down to write this comment i thought of new type of "test" - copying the "problematic directories" to an external NTFS formated hard drive. The first time I did this, it actually worked. I copied one of the crashy directories to my hd, opened nautilus so that it would generate the thumbnails for the pdf files contasined on the external HD and it workeded. Then I erased that same directory from the internal HD and then copied it back from the external HD. After this operation, nautilus managed to recreate the thumbnails on the internal drive without crashing. But I realized that this will not solve my problem because after my seciond attempt to do it with other directories, MY COMPUTER CRASHED while generating the thumbnails for the pdf files copied and stored on my external hard drive. Thanks god I finally m
[Desktop-packages] [Bug 1344996] Re: LibreOffice shows squares when the UI font does not support certain characters. It does not fallback to other fonts like the rest of apps.
Adolfo Jayme, You're right! I transfered my locally installed fonts from 12.04 when I installed 14.04 on my laptop, and an old version of Cantarell that I don't even remember where I got from. I think that the problem was fixed by just doing that, as LO started using the system wide installed Cantarell that comes from the Ubuntu 14.04 repository, but I also switched to Calibri just in case. Thank you for your assistance, as I would have never figured this out on my own (I didn't even know that I was using this two fonts specificaly as default system fonts). -- 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/1344996 Title: LibreOffice shows squares when the UI font does not support certain characters. It does not fallback to other fonts like the rest of apps. Status in “libreoffice” package in Ubuntu: Triaged Bug description: 1. Description: Ubuntu 14.04 LTS Release: 14.04 2. libreoffice-gtk: Installed: 1:4.2.4-0ubuntu2 Candidate: 1:4.2.4-0ubuntu2 Version table: *** 1:4.2.4-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.3~rc3-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3. I'v been hit with the strange bug for some time in LibreOffice under Ubuntu 14.04 Namely whenever I try to enter some string in LibreOffice Calc using non-latin characters, cyrillic in my case, the entry renders just fine in the cell, but it renders with a series of squares at the formula entry widget. The same happens with the search entry widget (ctrl+f). I'm hit by this bug when using both the default packages from the official Ubuntu repository, the packages from the LibreOffice PPAs but also packages that I've downloaded from the Libreoffice website. The first strange thing I've notied is that those same deb packages downloaded from the LibreOffice website work just fine under Ubuntu 12.04. Today I've done some testing (after removing the PPA packages so that ubuntu-bug would allow me to report this bug), and noticed that if I remove the libreoffice-gtk package, then I don't have this problem any more, except for the non exsistent theming and really ugly looking of LO. I conclude that the problem is not in the LibreoOffice itself but in some gtk library. I'm sending screenshots of the bug. One is taken under Ubuntu 12.04 where everything works fine, the other under Ubuntu 14.04 where this bug appears. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-gtk 1:4.2.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 19 18:51:50 2014 InstallationDate: Installed on 2014-04-19 (91 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1344996/+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 1344996] Re: Cyrillic entries render like squares in some LO widgets when libreoffice-gtk installed
Picture of how the same version of LibreOffice works as expected under Ubuntu 12.04. I know that this is somehow obvious but still. ** Attachment added: "LibreOffice Calc Under Ubuntu 12.04" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1344996/+attachment/4157067/+files/LO-Ubuntu12.04.png -- 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/1344996 Title: Cyrillic entries render like squares in some LO widgets when libreoffice-gtk installed Status in “libreoffice” package in Ubuntu: New Bug description: 1. Description: Ubuntu 14.04 LTS Release: 14.04 2. libreoffice-gtk: Installed: 1:4.2.4-0ubuntu2 Candidate: 1:4.2.4-0ubuntu2 Version table: *** 1:4.2.4-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.3~rc3-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3. I'v been hit with the strange bug for some time in LibreOffice under Ubuntu 14.04 Namely whenever I try to enter some string in LibreOffice Calc using non-latin characters, cyrillic in my case, the entry renders just fine in the cell, but it renders with a series of squares at the formula entry widget. The same happens with the search entry widget (ctrl+f). I'm hit by this bug when using both the default packages from the official Ubuntu repository, the packages from the LibreOffice PPAs but also packages that I've downloaded from the Libreoffice website. The first strange thing I've notied is that those same deb packages downloaded from the LibreOffice website work just fine under Ubuntu 12.04. Today I've done some testing (after removing the PPA packages so that ubuntu-bug would allow me to report this bug), and noticed that if I remove the libreoffice-gtk package, then I don't have this problem any more, except for the non exsistent theming and really ugly looking of LO. I conclude that the problem is not in the LibreoOffice itself but in some gtk library. I'm sending screenshots of the bug. One is taken under Ubuntu 12.04 where everything works fine, the other under Ubuntu 14.04 where this bug appears. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-gtk 1:4.2.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 19 18:51:50 2014 InstallationDate: Installed on 2014-04-19 (91 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1344996/+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 1344996] [NEW] Cyrillic entries render like squares in some LO widgets when libreoffice-gtk installed
Public bug reported: 1. Description: Ubuntu 14.04 LTS Release:14.04 2. libreoffice-gtk: Installed: 1:4.2.4-0ubuntu2 Candidate: 1:4.2.4-0ubuntu2 Version table: *** 1:4.2.4-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.3~rc3-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3. I'v been hit with the strange bug for some time in LibreOffice under Ubuntu 14.04 Namely whenever I try to enter some string in LibreOffice Calc using non-latin characters, cyrillic in my case, the entry renders just fine in the cell, but it renders with a series of squares at the formula entry widget. The same happens with the search entry widget (ctrl+f). I'm hit by this bug when using both the default packages from the official Ubuntu repository, the packages from the LibreOffice PPAs but also packages that I've downloaded from the Libreoffice website. The first strange thing I've notied is that those same deb packages downloaded from the LibreOffice website work just fine under Ubuntu 12.04. Today I've done some testing (after removing the PPA packages so that ubuntu-bug would allow me to report this bug), and noticed that if I remove the libreoffice-gtk package, then I don't have this problem any more, except for the non exsistent theming and really ugly looking of LO. I conclude that the problem is not in the LibreoOffice itself but in some gtk library. I'm sending screenshots of the bug. One is taken under Ubuntu 12.04 where everything works fine, the other under Ubuntu 14.04 where this bug appears. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-gtk 1:4.2.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 19 18:51:50 2014 InstallationDate: Installed on 2014-04-19 (91 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: "LibreOffice Calc Under Ubuntu 14.04" https://bugs.launchpad.net/bugs/1344996/+attachment/4157064/+files/LO-Ubuntu14.04.png -- 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/1344996 Title: Cyrillic entries render like squares in some LO widgets when libreoffice-gtk installed Status in “libreoffice” package in Ubuntu: New Bug description: 1. Description: Ubuntu 14.04 LTS Release: 14.04 2. libreoffice-gtk: Installed: 1:4.2.4-0ubuntu2 Candidate: 1:4.2.4-0ubuntu2 Version table: *** 1:4.2.4-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1:4.2.3~rc3-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 3. I'v been hit with the strange bug for some time in LibreOffice under Ubuntu 14.04 Namely whenever I try to enter some string in LibreOffice Calc using non-latin characters, cyrillic in my case, the entry renders just fine in the cell, but it renders with a series of squares at the formula entry widget. The same happens with the search entry widget (ctrl+f). I'm hit by this bug when using both the default packages from the official Ubuntu repository, the packages from the LibreOffice PPAs but also packages that I've downloaded from the Libreoffice website. The first strange thing I've notied is that those same deb packages downloaded from the LibreOffice website work just fine under Ubuntu 12.04. Today I've done some testing (after removing the PPA packages so that ubuntu-bug would allow me to report this bug), and noticed that if I remove the libreoffice-gtk package, then I don't have this problem any more, except for the non exsistent theming and really ugly looking of LO. I conclude that the problem is not in the LibreoOffice itself but in some gtk library. I'm sending screenshots of the bug. One is taken under Ubuntu 12.04 where everything works fine, the other under Ubuntu 14.04 where this bug appears. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-gtk 1:4.2.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 19 18:51:50 2014 InstallationDate: Installed on
[Desktop-packages] [Bug 1248368] Re: Volume up/down keyboard keys stoped working after gnome-settings-daemon package update
Sebastien, I'm not sure how, but I don't have this problem anymore. I thought that the offending patch was removed from the update, since I haven't been forced to stay to gnome-settings-daemon 3.4.2-0ubuntu0.6.4 for a very long time now. It might have something to do with me reinstalling the system (for reasons totally unrelated to this one). gnome-settings-daemon is at version 3.4.2-0ubuntu0.6.5, and the volume keys are working as expected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1248368 Title: Volume up/down keyboard keys stoped working after gnome-settings- daemon package update Status in “gnome-settings-daemon” package in Ubuntu: Incomplete Bug description: After updating gnome-settings-daemon from version 3.4.2-0ubuntu0.6.4 to version 3.4.2-0ubuntu0.6.5 the keyboard volume keys are not working. Pressing the keys does not produce the volume OSD, neither the volume is increased or decreased. The following packages were updated by synaptic: cjs (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise duplicity (0.6.18-0ubuntu3.2) to 0.6.18-0ubuntu3.3 gimp (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gimp-data (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gnome-settings-daemon (3.4.2-0ubuntu0.6.4) to 3.4.2-0ubuntu0.6.5 libcjs0c (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise libgimp2.0 (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa xkb-data (2.5-1ubuntu1.4) to 2.5-1ubuntu1.5 xserver-common-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 xserver-xorg-core-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 I suspected that the bug might be in xkb-data and/or gnome-settings-daemon. Downgrading the xkb-data package the previous version (2.5-1ubuntu1.4) didn't work. Downgrading the gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4) worked! Afterwords I upgraded xkb-data to the latest version (2.5-1ubuntu1.5) and left gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4). And this works!!! In conclusion there is some regression introduced into gnome-settings- daemon 3.4.2-0ubuntu0.6.5. lsb_release -rd Description: Ubuntu 12.04.3 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1248368/+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 1248368] Re: Volume up/down keyboard keys stoped working after gnome-settings-daemon package update
Also mapping the keys with the procedure from above works the same even with the broken 3.4.2-0ubuntu0.6.5 package installed, but as I said before, pressing the keys afterwards doesn't have any effect. The Play/Pause and the Stop keys are working fine -mapped as "Audio play"/"Audio pause" and "Audio stop" (right column labels) Launch media player key also works (It launches Rhytmbox), although the mapping shows (strangely) "Tools" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1248368 Title: Volume up/down keyboard keys stoped working after gnome-settings- daemon package update Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: After updating gnome-settings-daemon from version 3.4.2-0ubuntu0.6.4 to version 3.4.2-0ubuntu0.6.5 the keyboard volume keys are not working. Pressing the keys does not produce the volume OSD, neither the volume is increased or decreased. The following packages were updated by synaptic: cjs (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise duplicity (0.6.18-0ubuntu3.2) to 0.6.18-0ubuntu3.3 gimp (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gimp-data (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gnome-settings-daemon (3.4.2-0ubuntu0.6.4) to 3.4.2-0ubuntu0.6.5 libcjs0c (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise libgimp2.0 (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa xkb-data (2.5-1ubuntu1.4) to 2.5-1ubuntu1.5 xserver-common-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 xserver-xorg-core-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 I suspected that the bug might be in xkb-data and/or gnome-settings-daemon. Downgrading the xkb-data package the previous version (2.5-1ubuntu1.4) didn't work. Downgrading the gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4) worked! Afterwords I upgraded xkb-data to the latest version (2.5-1ubuntu1.5) and left gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4). And this works!!! In conclusion there is some regression introduced into gnome-settings- daemon 3.4.2-0ubuntu0.6.5. lsb_release -rd Description: Ubuntu 12.04.3 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1248368/+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 1248368] Re: Volume up/down keyboard keys stoped working after gnome-settings-daemon package update
Tormod, we are talking about a plain keyboard with multimedia keys. Manufacturer: Genius Product name: SlimStar310 Here's a link with a picture of it. http://pc.zoznam.sk/test-slim- klavesnic?page=1 If I open the keboard settings Keyboard->Shortcuts->Sound and media and do Volume up and Volume down key mapping: 1. I click on Volume up in the left column 2. "New accelerator.." is shown on the right collumn 3. If I press the keboard key for "Volume up", the right column shows "Audio raise volume" All this means that the keyboard sends a STANDARD code for increasing the volume level, so it's not that my keyboard is some kind of esoteric unstandard hardware. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1248368 Title: Volume up/down keyboard keys stoped working after gnome-settings- daemon package update Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: After updating gnome-settings-daemon from version 3.4.2-0ubuntu0.6.4 to version 3.4.2-0ubuntu0.6.5 the keyboard volume keys are not working. Pressing the keys does not produce the volume OSD, neither the volume is increased or decreased. The following packages were updated by synaptic: cjs (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise duplicity (0.6.18-0ubuntu3.2) to 0.6.18-0ubuntu3.3 gimp (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gimp-data (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gnome-settings-daemon (3.4.2-0ubuntu0.6.4) to 3.4.2-0ubuntu0.6.5 libcjs0c (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise libgimp2.0 (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa xkb-data (2.5-1ubuntu1.4) to 2.5-1ubuntu1.5 xserver-common-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 xserver-xorg-core-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 I suspected that the bug might be in xkb-data and/or gnome-settings-daemon. Downgrading the xkb-data package the previous version (2.5-1ubuntu1.4) didn't work. Downgrading the gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4) worked! Afterwords I upgraded xkb-data to the latest version (2.5-1ubuntu1.5) and left gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4). And this works!!! In conclusion there is some regression introduced into gnome-settings- daemon 3.4.2-0ubuntu0.6.5. lsb_release -rd Description: Ubuntu 12.04.3 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1248368/+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 1248368] Re: Volume up/down keyboard keys stoped working after gnome-settings-daemon package update
I also tried to submit the bug report using the "ubuntu-bug" command so that more data would be submited, but launchpad reported error (server down or something like that). I'm telling this in case someone gets a funny idea to mark the bug report invalid. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1248368 Title: Volume up/down keyboard keys stoped working after gnome-settings- daemon package update Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: After updating gnome-settings-daemon from version 3.4.2-0ubuntu0.6.4 to version 3.4.2-0ubuntu0.6.5 the keyboard volume keys are not working. Pressing the keys does not produce the volume OSD, neither the volume is increased or decreased. The following packages were updated by synaptic: cjs (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise duplicity (0.6.18-0ubuntu3.2) to 0.6.18-0ubuntu3.3 gimp (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gimp-data (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gnome-settings-daemon (3.4.2-0ubuntu0.6.4) to 3.4.2-0ubuntu0.6.5 libcjs0c (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise libgimp2.0 (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa xkb-data (2.5-1ubuntu1.4) to 2.5-1ubuntu1.5 xserver-common-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 xserver-xorg-core-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 I suspected that the bug might be in xkb-data and/or gnome-settings-daemon. Downgrading the xkb-data package the previous version (2.5-1ubuntu1.4) didn't work. Downgrading the gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4) worked! Afterwords I upgraded xkb-data to the latest version (2.5-1ubuntu1.5) and left gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4). And this works!!! In conclusion there is some regression introduced into gnome-settings- daemon 3.4.2-0ubuntu0.6.5. lsb_release -rd Description: Ubuntu 12.04.3 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1248368/+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 1248368] [NEW] Volume up/down keyboard keys stoped working after gnome-settings-daemon package update
Public bug reported: After updating gnome-settings-daemon from version 3.4.2-0ubuntu0.6.4 to version 3.4.2-0ubuntu0.6.5 the keyboard volume keys are not working. Pressing the keys does not produce the volume OSD, neither the volume is increased or decreased. The following packages were updated by synaptic: cjs (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise duplicity (0.6.18-0ubuntu3.2) to 0.6.18-0ubuntu3.3 gimp (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gimp-data (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gnome-settings-daemon (3.4.2-0ubuntu0.6.4) to 3.4.2-0ubuntu0.6.5 libcjs0c (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise libgimp2.0 (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa xkb-data (2.5-1ubuntu1.4) to 2.5-1ubuntu1.5 xserver-common-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 xserver-xorg-core-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 I suspected that the bug might be in xkb-data and/or gnome-settings-daemon. Downgrading the xkb-data package the previous version (2.5-1ubuntu1.4) didn't work. Downgrading the gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4) worked! Afterwords I upgraded xkb-data to the latest version (2.5-1ubuntu1.5) and left gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4). And this works!!! In conclusion there is some regression introduced into gnome-settings- daemon 3.4.2-0ubuntu0.6.5. lsb_release -rd Description:Ubuntu 12.04.3 LTS Release:12.04 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1248368 Title: Volume up/down keyboard keys stoped working after gnome-settings- daemon package update Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: After updating gnome-settings-daemon from version 3.4.2-0ubuntu0.6.4 to version 3.4.2-0ubuntu0.6.5 the keyboard volume keys are not working. Pressing the keys does not produce the volume OSD, neither the volume is increased or decreased. The following packages were updated by synaptic: cjs (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise duplicity (0.6.18-0ubuntu3.2) to 0.6.18-0ubuntu3.3 gimp (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gimp-data (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gnome-settings-daemon (3.4.2-0ubuntu0.6.4) to 3.4.2-0ubuntu0.6.5 libcjs0c (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise libgimp2.0 (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa xkb-data (2.5-1ubuntu1.4) to 2.5-1ubuntu1.5 xserver-common-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 xserver-xorg-core-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 I suspected that the bug might be in xkb-data and/or gnome-settings-daemon. Downgrading the xkb-data package the previous version (2.5-1ubuntu1.4) didn't work. Downgrading the gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4) worked! Afterwords I upgraded xkb-data to the latest version (2.5-1ubuntu1.5) and left gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4). And this works!!! In conclusion there is some regression introduced into gnome-settings- daemon 3.4.2-0ubuntu0.6.5. lsb_release -rd Description: Ubuntu 12.04.3 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1248368/+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 567828] Re: [i945g mesa] Blender 2.49b and 2.50 alpha2 UI rendering artifacts unless textured tiling disabled with driconf
Unfortunately I don't have that computer any more, the motherboard died 3 months after this bug report was created. The new one has a motherbord with GMA X4500, but I'm using it with an external NVidia card. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/567828 Title: [i945g mesa] Blender 2.49b and 2.50 alpha2 UI rendering artifacts unless textured tiling disabled with driconf Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: The default Intel driver used in Lucid is having some rendering problems in openGL applications. They can be easily noticed if you start Blender 2.49b or Blender 2.50 alpha2 downloaded from the main Blender website. I've been using Intel 2.9.1 driver from xorg-edgers when it was present there when I was using Karmic and I don't remember having such problems then and there. [Workaround] Disable texture tilling (with driconf) $lsb_release -rd Description: Ubuntu lucid (development branch) Release: 10.04 $apt-cache policy xserver-xorg-video-intel xserver-xorg-video-intel: Installed: 2:2.9.1-3ubuntu4 Candidate: 2:2.9.1-3ubuntu4 Version table: *** 2:2.9.1-3ubuntu4 0 500 http://ftp.kfki.hu/linux/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-video-intel 2:2.9.1-3ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Wed Apr 21 13:31:47 2010 DkmsStatus: MachineType: Shuttle Inc SK45 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-21-generic root=UUID=88416800-8b64-498a-96ab-cbf035390dbd ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-intel dmi.bios.date: 11/04/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: FM10 dmi.board.vendor: Shuttle Inc dmi.board.version: V10 dmi.chassis.type: 3 dmi.chassis.vendor: Shuttle Inc dmi.chassis.version: K dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd11/04/2008:svnShuttleInc:pnSK45:pvrV10:rvnShuttleInc:rnFM10:rvrV10:cvnShuttleInc:ct3:cvrK: dmi.product.name: SK45 dmi.product.version: V10 dmi.sys.vendor: Shuttle Inc system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-21-generic [lspci] 00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:3140] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/567828/+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 185300] Re: Rhythmbox Cannot Add or Update Podcast Feeds
Same problem with http://podcast.ubuntu-uk.org with the following subscription link: http://feeds.feedburner.com/UbuntuUkPodcastOgg- high?format=xml ** Attachment added: "debug.txt" https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/185300/+attachment/3139167/+files/debug.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/185300 Title: Rhythmbox Cannot Add or Update Podcast Feeds Status in “rhythmbox” package in Ubuntu: New Bug description: Binary package hint: rhythmbox Since the last update of Rhythmbox since Hardy Heron Alpha 3, I am unable to add new podcast feeds, or to update existing feeds. Attempting to do so produces an error stating, for e.g: 'There was a problem adding this podcast. Please verify the URL: http://www.psychoanalysisdownunder.com/whatsnew/lectures_2008?mode=rss' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/185300/+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 881955] Re: System monitor freezes up when switching to Processes tab
Packages from the xorg-edgers PPA also made Gnome Shell crash on my computer when switching from Windows to Applications "tab". I also noticed increased memory usage on my computer. In normal circumstances 31% of my system memory (out of 2GB) would be used after an X server reset (CTRL+ALT+BACKSPACE) and logging into Gnome Shell, but with the PPA enabled the memory usage refused to go under 51% after a reset (I tried it multiple times), and this happened after using the computer for a few hours. But I couldn't see what was using the memory because you know . Gnome system monitor isn't working :). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/881955 Title: System monitor freezes up when switching to Processes tab Status in “gnome-system-monitor” package in Ubuntu: Confirmed Bug description: Gnome-system-monitor 3.20 becomes unresponsive when I switch to the Processes tab. Any other tab works. This is reproducible as it happens every time. The app does not crash but seems to hang in a loop. I am running Oneiric x64 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-system-monitor 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Wed Oct 26 07:03:31 2011 ExecutablePath: /usr/bin/gnome-system-monitor InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110804) SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to oneiric on 2011-09-11 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/881955/+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 881955] Re: System monitor freezes up when switching to Processes tab
After doing some testing on my system, I realized that this problem occurs if you have xorg-edgers PPA activated. Purging the PPA solves the problem. This is the list of packages that the xorg-edgers PPA upgrades: intel-gpu-tools (1.0.2+git20100324-0ubuntu1) to 1.0.2+git20110729+3b10b7b-0ubuntu1~edgers libcairo-gobject2 (1.10.2-6ubuntu3) to 1.11.3+git2009.90b2fd34-0ubuntu0ricotz~oneiric0 libcairo-script-interpreter2 (1.10.2-6ubuntu3) to 1.11.3+git2009.90b2fd34-0ubuntu0ricotz~oneiric0 libcairo2 (1.10.2-6ubuntu3) to 1.11.3+git2009.90b2fd34-0ubuntu0ricotz~oneiric0 libcairo2-dev (1.10.2-6ubuntu3) to 1.11.3+git2009.90b2fd34-0ubuntu0ricotz~oneiric0 libdrm-dev (2.4.26-1ubuntu1) to 2.4.27+git2004.961bf9b5-0ubuntu0sarvatt~oneiric libdrm-intel1 (2.4.26-1ubuntu1) to 2.4.27+git2004.961bf9b5-0ubuntu0sarvatt~oneiric libdrm-nouveau1a (2.4.26-1ubuntu1) to 2.4.27+git2004.961bf9b5-0ubuntu0sarvatt~oneiric libdrm-radeon1 (2.4.26-1ubuntu1) to 2.4.27+git2004.961bf9b5-0ubuntu0sarvatt~oneiric libdrm2 (2.4.26-1ubuntu1) to 2.4.27+git2004.961bf9b5-0ubuntu0sarvatt~oneiric libegl1-mesa (7.11-0ubuntu3) to 7.12.0~git2009.1d1c0fa2-0ubuntu0sarvatt~oneiric libegl1-mesa-dev (7.11-0ubuntu3) to 7.12.0~git2009.1d1c0fa2-0ubuntu0sarvatt~oneiric libegl1-mesa-drivers (7.11-0ubuntu3) to 7.12.0~git2009.1d1c0fa2-0ubuntu0sarvatt~oneiric libffi6 (3.0.11~rc1-2) to 3.0.11~rc1-5~oneiric1 libgbm1 (7.11-0ubuntu3) to 7.12.0~git2009.1d1c0fa2-0ubuntu0sarvatt~oneiric libgl1-mesa-dev (7.11-0ubuntu3) to 7.12.0~git2009.1d1c0fa2-0ubuntu0sarvatt~oneiric libgl1-mesa-dri (7.11-0ubuntu3) to 7.12.0~git2009.1d1c0fa2-0ubuntu0sarvatt~oneiric libgl1-mesa-glx (7.11-0ubuntu3) to 7.12.0~git2009.1d1c0fa2-0ubuntu0sarvatt~oneiric libglapi-mesa (7.11-0ubuntu3) to 7.12.0~git2009.1d1c0fa2-0ubuntu0sarvatt~oneiric libglu1-mesa (7.11-0ubuntu3) to 7.12.0~git2009.1d1c0fa2-0ubuntu0sarvatt~oneiric libglu1-mesa-dev (7.11-0ubuntu3) to 7.12.0~git2009.1d1c0fa2-0ubuntu0sarvatt~oneiric libkms1 (2.4.26-1ubuntu1) to 2.4.27+git2004.961bf9b5-0ubuntu0sarvatt~oneiric libopenvg1-mesa (7.11-0ubuntu3) to 7.12.0~git2009.1d1c0fa2-0ubuntu0sarvatt~oneiric libpciaccess0 (0.12.1-2) to 0.12.902-0ubuntu0ricotz~oneiric0 libpixman-1-0 (0.22.2-1) to 0.24.0-1~oneiric1 libpixman-1-dev (0.22.2-1) to 0.24.0-1~oneiric1 libwayland0 (0.1.0~0.2-0ubuntu3) to 0.1.0~git20111027.7e57dc14-0ubuntu0ricotz~oneiric linux-libc-dev (3.0.0-13.22) to 3.1.0-2.2 linux-tools-common (3.0.0-13.22) to 3.1.0-2.2 mesa-common-dev (7.11-0ubuntu3) to 7.12.0~git2009.1d1c0fa2-0ubuntu0sarvatt~oneiric nvidia-current (285.05.09-0ubuntu1~oneiric~xup1) to 290.06-0ubuntu1~xedgers~oneiric1 nvidia-settings (285.05.09-0ubuntu1~oneiric~xup1) to 290.06-0ubuntu1~xedgers~oneiric1 x11-common (1:7.6+7ubuntu7) to 1:7.6+7ubuntu7edgers2 xorg (1:7.6+7ubuntu7) to 1:7.6+7ubuntu7edgers2 xserver-common (2:1.10.4-1ubuntu4.2) to 2:1.11.2+git2009+server-1.11-branch.34bb83b9-0ubuntu0ricotz~oneiric xserver-xorg (1:7.6+7ubuntu7) to 1:7.6+7ubuntu7edgers2 xserver-xorg-core (2:1.10.4-1ubuntu4.2) to 2:1.11.2+git2009+server-1.11-branch.34bb83b9-0ubuntu0ricotz~oneiric xserver-xorg-input-all (1:7.6+7ubuntu7) to 1:7.6+7ubuntu7edgers2 xserver-xorg-input-evdev (1:2.6.0-1ubuntu13) to 1:2.6.0+git20110912.070f30e0-0ubuntu0sarvatt xserver-xorg-input-mouse (1:1.7.1-1) to 1:1.7.1+git2009.b6565197-0ubuntu0sarvatt~oneiric xserver-xorg-input-synaptics (1.4.1-1ubuntu2) to 1.5.99+git2010.cefc85ad-0ubuntu0ricotz~oneiric xserver-xorg-input-vmmouse (1:12.7.0-2) to 1:12.7.0+git2009.fd140bfb-0ubuntu0sarvatt~oneiric xserver-xorg-input-wacom (1:0.11.0-0ubuntu2) to 1:0.11.0-0ubuntu2ricotz1 xserver-xorg-video-all (1:7.6+7ubuntu7) to 1:7.6+7ubuntu7edgers2 xserver-xorg-video-apm (1:1.2.3-2) to 1:1.2.3+git2009.6f8a776f-0ubuntu0sarvatt~oneiric xserver-xorg-video-ark (1:0.7.3-2) to 1:0.7.3+git2009.9d3769be-0ubuntu0sarvatt~oneiric xserver-xorg-video-ati (1:6.14.99~git20110811.g93fc084-0ubuntu1) to 1:6.14.99+git2006.5ec34ed9-0ubuntu0sarvatt xserver-xorg-video-chips (1:1.2.4-1) to 1:1.2.4+git2009.8a5ea07f-0ubuntu0sarvatt~oneiric xserver-xorg-video-cirrus (1:1.3.2-2ubuntu7) to 1:1.3.2+git20110912.e4f80ffd-0ubuntu0sarvatt xserver-xorg-video-fbdev (1:0.4.2-3ubuntu6) to 1:0.4.2+git2009.a8721393-0ubuntu0sarvatt~oneiric xserver-xorg-video-geode (2.11.12-2) to 2.11.12-2ubuntu0sarvatt xserver-xorg-video-i128 (1:1.3.4-2) to 1:1.3.4+git2009.0e357623-0ubuntu0sarvatt~oneiric xserver-xorg-video-i740 (1:1.3.2-4) to 1:1.3.2+git2009.87da594b-0ubuntu0sarvatt~oneiric xserver-xorg-video-intel (2:2.15.901-1ubuntu2.1) to 2:2.16.901+git2009.436a7868-0ubuntu0sarvatt~oneiric xserver-xorg-video-mach64 (6.9.0-1) to 6.9.0+git2009.0de23432-0ubuntu0sarvatt~oneiric xserver-xorg-video-mga (1:1.4.13.dfsg-3build1) to 1:1.4.13.dsfg+git20110928.07792ef4-0ubuntu0sarvatt xserver-xorg-video-neomagic (1:1.2.5-2) to 1:1.2.5+git2009.f2a771c6-0ubuntu0sarvatt~oneiric xs
[Desktop-packages] [Bug 880471] [NEW] Crossfade between tracks option crashes Rhythmbox when flac tracks are played
Public bug reported: When crossfade between tracks is enabled in Rhythmbox and when there is a list of flac tracks are played results in Rhythmbox crash. Not only that, but it crashes the whole Gnome Shell. I have Media player indicator shell extension installed and I don't know if that is somehow connected to the whole Gnome Shell crash. Also worth noticing is that Rhythmbox displays some weird bitrate information for some of the flac tracks. For some of them "Quality" says Lossless while for others it reports numbers like 43kbps, 370kbps etc. Considering the fact that Nautilus Properties for this tracks also reports the same bitrates maybe the problem is not directly in Rhythmbox but in the GStreamer backend that as far as I know both Nautilus and Rhythmbox use. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: rhythmbox 2.90.1~20110908-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Sun Oct 23 19:08:37 2011 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) SourcePackage: rhythmbox UpgradeStatus: Upgraded to oneiric on 2011-10-10 (12 days ago) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 oneiric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/880471 Title: Crossfade between tracks option crashes Rhythmbox when flac tracks are played Status in “rhythmbox” package in Ubuntu: New Bug description: When crossfade between tracks is enabled in Rhythmbox and when there is a list of flac tracks are played results in Rhythmbox crash. Not only that, but it crashes the whole Gnome Shell. I have Media player indicator shell extension installed and I don't know if that is somehow connected to the whole Gnome Shell crash. Also worth noticing is that Rhythmbox displays some weird bitrate information for some of the flac tracks. For some of them "Quality" says Lossless while for others it reports numbers like 43kbps, 370kbps etc. Considering the fact that Nautilus Properties for this tracks also reports the same bitrates maybe the problem is not directly in Rhythmbox but in the GStreamer backend that as far as I know both Nautilus and Rhythmbox use. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: rhythmbox 2.90.1~20110908-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Sun Oct 23 19:08:37 2011 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) SourcePackage: rhythmbox UpgradeStatus: Upgraded to oneiric on 2011-10-10 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/880471/+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 880471] Re: Crossfade between tracks option crashes Rhythmbox when flac tracks are played
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/880471 Title: Crossfade between tracks option crashes Rhythmbox when flac tracks are played Status in “rhythmbox” package in Ubuntu: New Bug description: When crossfade between tracks is enabled in Rhythmbox and when there is a list of flac tracks are played results in Rhythmbox crash. Not only that, but it crashes the whole Gnome Shell. I have Media player indicator shell extension installed and I don't know if that is somehow connected to the whole Gnome Shell crash. Also worth noticing is that Rhythmbox displays some weird bitrate information for some of the flac tracks. For some of them "Quality" says Lossless while for others it reports numbers like 43kbps, 370kbps etc. Considering the fact that Nautilus Properties for this tracks also reports the same bitrates maybe the problem is not directly in Rhythmbox but in the GStreamer backend that as far as I know both Nautilus and Rhythmbox use. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: rhythmbox 2.90.1~20110908-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Sun Oct 23 19:08:37 2011 ExecutablePath: /usr/bin/rhythmbox InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426) SourcePackage: rhythmbox UpgradeStatus: Upgraded to oneiric on 2011-10-10 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/880471/+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
