[Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
I was getting random freezes on a Dell Latitude E7450 with Intel HD Graphics 5500, with no hints as to the cause in logs that I could find. Freezes could happen multiple times a day when in heavy use, but often more like once a week. I followed the advice in #42 a month ago and have had no freezes since (fingers crossed!). Currently on 18.04.2 LTS with 4.15.0-50-generic, but also had freezes on 16.04 LTS, starting around autumn 2018. Although had been using this laptop since 2015 without problem before that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672157] Re: package mouseemu 0.16-0ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 (/var/lib/dpkg/info/mouseemu.postinst: MAKEDEV:
Attaching patch. Explicit work-around in the mean time: sudo apt-get purge mouseemu sudo apt-get install makedev mouseemu ** Patch added: "mouseemu_makedev_depends.patch" https://bugs.launchpad.net/ubuntu/+source/mouseemu/+bug/1672157/+attachment/5237222/+files/mouseemu_makedev_depends.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672157 Title: package mouseemu 0.16-0ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 (/var/lib/dpkg/info/mouseemu.postinst: MAKEDEV: not found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mouseemu/+bug/1672157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672157] Re: package mouseemu 0.16-0ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 (/var/lib/dpkg/info/mouseemu.postinst: MAKEDEV:
The fix is to install the makedev package first, which provides the MAKEDEV script that's required as part of the package setup. If a Ubuntu maintainer could add makedev to the dependencies for mouseemu, that would be great :-). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672157 Title: package mouseemu 0.16-0ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 (/var/lib/dpkg/info/mouseemu.postinst: MAKEDEV: not found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mouseemu/+bug/1672157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 943195] Re: xpdf.real crashed with SIGSEGV in GooHash::hash()
Following comment #27 I rebuilt the precise source package using the patch from http://bugs.debian.org/cgi- bin/bugreport.cgi?msg=49;mbox=yes;bug=658264 and the crashes stopped for me. I hope a fix can make it into 12.04.1 -- it would be frustrating if the LTS Ubuntu boxes that will be around for years all have a completely broken xpdf. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/943195 Title: xpdf.real crashed with SIGSEGV in GooHash::hash() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xpdf/+bug/943195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 694910] Re: Regression: patch to bug 539477 breaks Super+P keybindings
@Vinh sorry I didn't see your request. I have a later version than you, 3.2.2. If you have an earlier Ubuntu release, maybe try the work-around I linked to in the first comment? The good news is that this issue may have been fixed in Ubuntu "precise" 12.04. I just installed that on a new machine and I don't seem to have the issue. Although the offending code still seems to be there, so I'm not sure what's going on. I don't currently have the time to upgrade the machines that had the issue before. BTW in gnome-settings-daemon 3.4.2, which comes with Ubuntu 12.04, acme.h got renamed shortcuts-list.h -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/694910 Title: Regression: patch to bug 539477 breaks Super+P keybindings To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/694910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 694910] Re: Regression: patch to bug 539477 breaks Super+P keybindings
Correction: one now needs to disable the media keys plugin instead of the xrandr plugin (using dconf) to prevent p being stolen. This new fix breaks different things to before. For my machine I've recompiled gnome-settings-daemon to get rid of the problem. If anyone else wants to do the same, the offending shortcut is in acme.h, search for VIDEO_OUT_KEY. [Finding this file reminded me that media key handling used to be in a standalone program called acme. It's a shame that gnome moved away from providing simple standalone programs that could be taken in isolation.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/694910 Title: Regression: patch to bug 539477 breaks Super+P keybindings To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/694910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 694910] Re: Regression: patch to bug 539477 breaks Super+P keybindings
I just wasted a bunch more time because of this bug. The xrandr plugin to gnome-settings-daemon is now configured in dconf not in gconf: http://askubuntu.com/questions/68463/how-to-disable-global-super-p-shortcut Because there's no option to stop the keybinding being stolen, one still has to disable it entirely. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/694910 Title: Regression: patch to bug 539477 breaks Super+P keybindings To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/694910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 694910] Re: Regression: patch to bug 539477 breaks Super+P keybindings
I applied the workaround in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/539477/comments/64 to make super+p work again in Maverick at the expense of breaking the Gnome monitor settings GUI. For those suffering, possible workarounds to the breakage the workaround causes are: a) to change monitor settings with the Gnome control panel, temporarily undo the workaround; or b) drive xrandr from the command line or use the arandr GUI front-end to xrandr instead of the Gnome GUI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/694910 Title: Regression: patch to bug 539477 breaks Super+P keybindings -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539477] Re: Video out hot key sends super + p + return on many upcoming Dell & HP systems
Again, the super+p keybinding is broken for all user applications when running gnone-settings-daemon, and the option to fix the problem is not discoverable (and may have other side effects). I disabled all the keybindings in gnome-keybinding-properties and performed various other hair-pulling before discovering the cause was this "fix". The committed patch causes a frustrating regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/539477 Title: Video out hot key sends super + p + return on many upcoming Dell & HP systems -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191452] Re: C standard library functions div() or ldiv() produces incorrect answers when compiled with tcc
The fork available at: http://www.landley.net/code/tinycc/ doesn't exhibit this bug. (I don't know anything else about the differences between the versions, or the back-story regarding the fork.) -- C standard library functions div() or ldiv() produces incorrect answers when compiled with tcc https://bugs.launchpad.net/bugs/191452 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191452] [NEW] C standard library functions div() or ldiv() produces incorrect answers when compiled with tcc
Public bug reported:
Binary package hint: tcc
Both div and ldiv give spurious results when compiled with tcc. For
example, the following program:
#include
#include
int main(int argc, char **argv)
{
div_t ans = div(27, 10);
printf("quot = %d; rem = %d\n", ans.quot, ans.rem);
return 0;
}
This should (and does when compiled with gcc) print:
quot = 2; rem = 7
When compiling with tcc I get:
quot = 8; rem = 7
I am running gutsy and was using the tcc that ships with that. I also built and
installed the version from hardy:
tcc 0.9.24~cvs20070502-2
Same results.
** Affects: tcc (Ubuntu)
Importance: Undecided
Status: New
--
C standard library functions div() or ldiv() produces incorrect answers when
compiled with tcc
https://bugs.launchpad.net/bugs/191452
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62322] Re: en_GB.UTF-8: Missing text in "object" context menu
Also using LANG=en_GB.UTF-8, the zoom options: Page Width Optimal Entire Page are replaced with blank text in the zoom drop down list and the zoom dialog in at least oowriter and oodraw. The problem is fixed by changing to en_US.UTF-8. Presumably someone that knows how needs to thoroughly review openoffice .org-l10n-en-gb (?) -- en_GB.UTF-8: Missing text in "object" context menu https://launchpad.net/bugs/62322 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71407] Re: gataxx won't save computer difficulty above 3
Patch attached for minimal fix-up. ** Attachment added: "Fixes gconf description in schema and input range in properties code." http://librarian.launchpad.net/5056187/PATCH -- gataxx won't save computer difficulty above 3 https://launchpad.net/bugs/71407 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71407] gataxx won't save computer difficulty above 3
Public bug reported: If a computer player is set to the highest difficulty level this is not remembered on closing and reopening gataxx. Instead the difficulty gets reset to "Medium". Looking in gconf-editor the blacklevel or whitelevel keys are correctly set to 5, but the comment at the bottom says that only levels 0 or 1--3 are expected. ** Affects: gnome-games (Ubuntu) Importance: Undecided Status: Unconfirmed -- gataxx won't save computer difficulty above 3 https://launchpad.net/bugs/71407 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63408] Re: failing to find fonts: dexconf writes bogus FontPaths
Dave Love's patch works for me (thanks very much). I'm left wondering why this hasn't been fixed. -- failing to find fonts: dexconf writes bogus FontPaths https://launchpad.net/bugs/63408 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32963] Re: Xv movies on 810/i945 gives horrible color, Gamma
I've also tried totem-gstreamer, which also exhibits the bug as above. -- Xv movies on 810/i945 gives horrible color, Gamma https://launchpad.net/bugs/32963 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32963] Re: Xv movies on 810/i945 gives horrible color, Gamma
I have similar washed out videos under some circumstances with an "Intel Corporation 82852/855GM Integrated Graphics Device" using the i810 driver. This is a Dell Inspiron 710m. I'm running 6.06 LTS originally installed from an official CD with whatever updates apt offered me. My impression is that it is a totem-xine and gxine bug. If I watch movies with xine (from the xine-ui package) or mplayer after an X restart then everything is fine. xvattr information (given later) is not changed by running xine or mplayer. Movies under totem (totem-xine) are washed out. The values reported by xvattr change, but are reset after closing totem. Moves subsequently play ok in xine or mplayer. Totem can also play movies fine if xvattr values are fixed after starting totem. Movies under gxine are washed out, xvattr values are changed (although not to same values as by totem) and stay changed. Movies in xine or mplayer are washed out until an X restart or xvattr stuff changed back by hand. Again gxine plays fine if fix xvattr values by hand while gxine running. I get the following xvattr output after X restart: and stays the same after running xine(-ui) or totem(-xine): % xvattr Found Xv 2.2 Adaptor: 0 Name: Intel(R) Video Overlay Port: 73 Name: XV_COLORKEY Flags: XvGettable XvSettable Min value: 0 Max value: 16777215 Current value: 66046 Name: XV_BRIGHTNESS Flags: XvGettable XvSettable Min value: -128 Max value: 127 Current value: -5 Name: XV_CONTRAST Flags: XvGettable XvSettable Min value: 0 Max value: 255 Current value: 48 The values are reset after closing totem, but while it is running I get: % xvattr Found Xv 2.2 Adaptor: 0 Name: Intel(R) Video Overlay Port: 73 Name: XV_COLORKEY Flags: XvGettable XvSettable Min value: 0 Max value: 16777215 Current value: 66046 Name: XV_BRIGHTNESS Flags: XvGettable XvSettable Min value: -128 Max value: 127 Current value: -1 Name: XV_CONTRAST Flags: XvGettable XvSettable Min value: 0 Max value: 255 Current value: 127 After running (and closing) gxine I get: % xvattr Found Xv 2.2 Adaptor: 0 Name: Intel(R) Video Overlay Port: 73 Name: XV_COLORKEY Flags: XvGettable XvSettable Min value: 0 Max value: 16777215 Current value: 66046 Name: XV_BRIGHTNESS Flags: XvGettable XvSettable Min value: -128 Max value: 127 Current value: 0 Name: XV_CONTRAST Flags: XvGettable XvSettable Min value: 0 Max value: 255 Current value: 128 I've been fixing color washouts by running: xvattr -a XV_CONTRAST -v 48 ; xvattr -a XV_BRIGHTNESS -v -5 Why (with the default settings, which I haven't touched) don't totem/gxine just leave the xvattr settings alone? -- Xv movies on 810/i945 gives horrible color, Gamma https://launchpad.net/bugs/32963 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
