[Bug 1953076] [NEW] Ubuntu 20.04 - NVIDIA GPU consuming power even when using only integrated graphics card (Intel iGPU)

2021-12-02 Thread Tom B
Public bug reported: The issue is pretty simple: using Nvidia X Sever Settings GUI to switch from NVIDIA GPU to Intel iGPU doesn't work and the NVIDIA GPU does still consume some power after rebooting and, as a consequence, it generates uneccesary heat. Same thing (obviously) happens if I use

[Bug 1765363] Re: prime-select intel is not powering off the nvidia card

2021-12-02 Thread Tom B
This is still happening even on Ubuntu 20.04. I even tried installing without "Additional Drivers" checked and the problem is still there. I tried some workarounds posted here but they don't work or they might be out of date. Any update on this? Zephyrus M16 - 11800H - 3070 - Nvidia Driver 470

[Bug 1306657] Re: libmms vulnerability

2014-04-12 Thread Tom B
There is no CVE number. I am one of the libmms maintainers and was privately notified of this vulnerability. I can provide the details, if needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-04-11 Thread Tom B
I've also tested this using Juno (the version included in Zend Studio 10) and unfortunately share auspex's experience, it doesn't solve the issue for me. I also tried explicitly launching the application with an affinity: taskset 0x0001 zend-studio with the same reslult. -- You received

[Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-04-10 Thread Tom B
It's probably worth mentioning that with the latest Eclipse (Kepler) this bug does not occur. Perhaps looking at the differences between what happens on close in the find dialog in Kepler and Juno will shed some light on what is causing the crash. -- You received this bug notification because

[Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-02-20 Thread Tom B
Unfortunately running Eclipse via sudo does not fix the issue for me and I get the exact same crash: Stack: [0x7f252c76,0x7f252c861000], sp=0x7f252c85d040, free space=1012k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) C

[Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-02-20 Thread Tom B
This may also be relevant: It doesn't seem to be an Ubuntu/Debian based distro specific bug. I also have an Arch Linux installation and it happens on that as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-01-28 Thread Tom B
I'm not sure this is helpful or not but: I don't have Unity installed. I'm running Linux Mint which is built from Ubuntu and I'm running KDE. Whether that rules out a unity bug or not I don't know. Setting UBUNTU_MENUPROXY has no effect at all. Using

[Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-01-23 Thread Tom B
Has anyone managed to track the package which is the source of this bug? Here's my understanding so far: It's not an Eclipse bug as the same version of Eclipse running on Ubuntu 13.04 does not suffer the problem It doesn't appear to stem directly from oxygen-gtk as the QtCurve theme suffers

[Bug 1241101] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10

2014-01-15 Thread Tom B
That's a different bug. I can confirm that does fix several issues with oxygen-gtk but not the g_object_get_qdata crash. See https://bugs.kde.org/show_bug.cgi?id=329814 for the g_object_get_qdata crash. ** Bug watch added: KDE Bug Tracking System #329814

[Bug 343490] [NEW] The partition utility in the setup program reports a bogus disk percentage used.

2009-03-16 Thread Tom B.
Public bug reported: In Ubuntu 9.04 (Jaunty Jackalope) Alpha 6, the disk partitioner reports a bogus percentage disk space used. It is probably a really easy bug to fix, if someone can give me a rough idea of where to find the source code. I think the disk utility is reporting the disk size as

[Bug 317781] Re: Ext4 data loss

2009-03-15 Thread Tom B.
@Volodymyr I finished recompiling the kernel with Theodore Ts'o patches, and reran Volodymyr's test cases with the patched kernel. The results are: File System Method Performance (Typical, Minimum, Maximum) #Lost %Lost ext4patch 1 0.440.410.501 1.00% ext4patch

[Bug 343490] Re: The partition utility in the setup program reports a bogus disk percentage used.

2009-03-15 Thread Tom B.
** Attachment added: PictureOfPercentage http://launchpadlibrarian.net/23897297/UbuntuInstallBug.png -- The partition utility in the setup program reports a bogus disk percentage used. https://bugs.launchpad.net/bugs/343490 You received this bug notification because you are a member of

[Bug 317781] Re: Ext4 data loss

2009-03-14 Thread Tom B.
@Volodymyr I did some experimenting with your test cases. My results so far are: File System Method Performance (Typical, Minimum, Maximum) #Lost %Lost ext31 0.430.420.501 1.00% ext32 0.320.300.330 0.00% ext33 0.190.16

[Bug 317781] Re: Ext4 data loss

2009-03-14 Thread Tom B.
@CowBoyTim I agree with you. I work with real-time industrial systems, where the shop floor systems are considered unreliable. We have all the same issues as a regular desktop user, except our users have bigger hammers. The attraction of ext3 was the journalling with the ordered data mode. If