[Bug 1911860] Re: coturn does not start after update of Jan 13 '21 (20.04.1 LTS)
I would NOT recommend, using /lib/systemd/system/coturn.service directly. It's bound to be overwritten the next time the package ist updated. Changes to systemc units should go in /etc/systemd/system/coturn.service.d/override.conf and can best be applied using the command systemctl edit coturn The overide.conf file needs only the two lines mentioned above: [Service] AmbientCapabilities=CAP_NET_BIND_SERVICE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911860 Title: coturn does not start after update of Jan 13 '21 (20.04.1 LTS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coturn/+bug/1911860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1294854] Re: Clonezilla - “Box” is an unknown partition device
Got the error today for the first time (admittedly not from Ubuntu, but from PartedMagic 2015-03-06) Anyways, I got it reproduced, AND it's (at least in my case) a not-bug. Steps to reproduce: - ATA Secure Erase an SSD - Start Clonezilla without restarting the computer first and without updating the in-kernel partition-list - The message appears: "Box" is an unknown partition device Steps to AVOID the message: - ATA Secure Erase an SSD - execute "sudo partprobe" (notice that the information in /proc/partitions STILL contains the no-longer-existing partitions on the just erased device) (think it might be a bug in partprobe? shouldn't that delete non-existing partitions as well as register new ones?) - use gparted or fdisk to create (at least) an empty partition-table on the device (confirm that cat /proc/partitions now shows /dev/sda without any partitions) - start clonezilla again (notice that while the above error-message doesn't appear, clonezilla doesn't see my external harddisk - although I CAN mount the partitions manually *sigh*) - restart the computer (again with Parted Magic) - Start Clonezilla again - and notice, the external harddisk STILL doesn't appear - give up with PartedMagic and reboot to Clonezilla Live (2.4.2-something) - finally be able to restore the image OK, apologies for the lengthy "write as I go" procedure - obviously the middle few steps can be eliminated as they don't work. The main point was: the original "bug" isn't a bug, at least not in clonezilla and not how I used it. And yes, I did notice that the original submitter said, he wanted to image FROM an SSD, and not TO an SSD, so it might be unrelated after all, however in my case at least, it was easy to circumvent the error- message. Greetings, Dweia -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1294854 Title: Clonezilla - “Box” is an unknown partition device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clonezilla/+bug/1294854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317599] Re: Evince doesn't show fi-ligatures in a pdf file when tex-gyre is installed
@madbiologist: thanksa lot! This fixes the bug for me in Ubuntu 12.04 (for both Times and Helvetica) dweia@zeitlinie:~$ fc-match Helvetica n019003l.pfb: Nimbus Sans L Regular dweia@zeitlinie:~$ fc-match Times n021003l.pfb: Nimbus Roman No9 L Regular -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317599 Title: Evince doesn't show fi-ligatures in a pdf file when tex-gyre is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1317599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 461354] Re: finger doesn't support utf8 characters
Bug still present in Ubuntu 14.04 - a working patch to the bug was already made in 2005 though: https://bugzilla.redhat.com/show_bug.cgi?id=174352 https://bugzilla.redhat.com/attachment.cgi?id=122281 (The only line that needs to be corrected is the position of the #include locale.h) (See attachment for patch that works in Ubuntu) ** Bug watch added: Red Hat Bugzilla #174352 https://bugzilla.redhat.com/show_bug.cgi?id=174352 ** Patch added: Patch to display UTF-8 characters correctly https://bugs.launchpad.net/ubuntu/+source/bsd-finger/+bug/461354/+attachment/4219323/+files/widechar.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/461354 Title: finger doesn't support utf8 characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsd-finger/+bug/461354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 164054] Re: [needs-packaging] Lexmark 4550 all in one driver
I am pretty sure, this bug / feature request can be closed - I have searched the Lexmark-sites high and low, there's no Linux Driver Kit anywhere any more. Haven't even found the linux-driver any more that I later found on an old CD, it seems Lexmark removed their Linux-support completely. :( Best bet for drivers is http://www.openprinting.org/printers/manufacturer/Lexmark -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/164054 Title: [needs-packaging] Lexmark 4550 all in one driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/164054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727620] Re: [Radeon HD 5650 and 5470] Driver crash during recovery boot and in normal boot (Regression from 2.6.38-3 to -4)
Sorry, I got sidetracked while getting a set of logs. However, some (yet slightly vague) findings may be useful - even if debugging gets maybe even harder: Firstly: the computer (BIOS or whatever) behaves differently when external power is connected or only battery used, and secondly: it behaves differently depending on the last state of the vgaswitcheroo BEFORE the reboot. I need to do more testing regarding the former (probably frequency of crashes higher with external power), but the latter seemed to me pretty consistently only crashing after echo OFF /sys/kernel/debug/vgaswitcheroo/switch. I did yesterday a kernel-update to 2.6.38-8, I'll try to reproduce the findings and will try to see if anything changed in the behaviour. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Driver crash during recovery boot and in normal boot (Regression from 2.6.38-3 to -4) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727620] Re: [Radeon HD 5650 and 5470] Driver crash during recovery boot and in normal boot (Regression from 2.6.38-3 to -4)
Chris Halse Rogers wrote in #22: This does look a lot like some bad interaction between i915/radeon I agree - I did some more testing and placed an entry for the radeon- module into /etc/initramfs-tools/modules, and voilá - no crash! (after booting into X I can't get back to the text-console, but that's possibly another issue). What proves the bad interaction even more is: when also placing i915 into /etc/initramfs-tools/modules BEFORE radeon, booting isn't possible at all any more, but when placing i915 AFTER radeon, booting is possible, but I got a black screen (as in totally black, that is: no backlight) until X starts up. I'll try to get logs of four different initrd-configurations (though I doubt I'll be able to record the one where the crash occurs already during running of initrd...) P.S. off-topic, I knew a cjwatson once - hi Kamion ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Driver crash during recovery boot and in normal boot (Regression from 2.6.38-3 to -4) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727620] Re: [Radeon HD 5650 and 5470] Driver crash during recovery boot and in normal boot (Regression from 2.6.38-3 to -4)
Bryce Harrington wrote in #25 Upstream would like to see if setting the video to the radeon/descrete setting in the BIOS configuration makes it function properly. Answer: Yes it does. I tried that a while ago already, but can't (don't want to) use that for regular running, because the radeon-card makes the laptop-battery ruin out too fast. I read also that there's a patched/hacked BIOS somewhere that allows to switch off the radeon-card via BIOS, but if it can be solved with software I'd prefer that ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Driver crash during recovery boot and in normal boot (Regression from 2.6.38-3 to -4) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727620] Re: [Radeon HD 5650 and 5470] Driver crash during recovery boot and in normal boot (Regression from 2.6.38-3 to -4)
Unfortunately I discovered yesterday, that I lied. Wehn used without battery (this is a Aspire 3820TG laptop) and connected power-cord, the crash occurs also with kernel 2.6.36-1. Probably the BIOS does something to/with the graphics-cards, when external power is connected. All the previous tests had been running on battery-power. Couldn't yet test the 2.6.35 kernel, since I removed it already- need to reinstall that and see what happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Driver crash during recovery boot and in normal boot (Regression from 2.6.38-3 to -4) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 727620] Re: [Radeon HD 5650 and 5470] Driver crash during recovery boot and in normal boot (Regression from 2.6.38-3 to -4)
Bryce Harrington wrote on 2011-03-04:[...] That suggests a regression in the kernel between 2.6.38-3 and -4 The error must have occured a lot earlier. I tried a bunch of different kernels, each with the (at the moment) most recent version (highest number after the dash): 2.6.35-25 - works 2.6.36-1 - works 2.6.37-12 - crashes most of the time 2.6.38-7 - crashes most of the time I also tried some other versions, including the mentioned 2.6.38-3, but no luck there for me. There's another bug, which may or may not be related, and which got apparently fixed with kernel 2.6.37, maybe thereby introducing this problem with the crashes? This older problem causes entries like the following in the kernel log when shutting down or rebooting the system. kernel: [ 36.068256] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting kernel: [ 36.068719] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CF42 (len 72, WS 0, PS 0) @ 0xCF71 kernel: [ 41.070113] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting kernel: [ 41.070654] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CB20 (len 62, WS 0, PS 0) @ 0xCB3C kernel: [ 46.271694] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting kernel: [ 46.272333] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CB20 (len 62, WS 0, PS 0) @ 0xCB3C These entries occur only in kernel 2.6.35 once per second, in 2.6.36 every 5 seconds and disappear altogether in 2.6.37 P.S. I don't think the bug has to do with xserver-xorg at all - it's most probably the radeon kernel-module, since the errors occur long before X is starting. Also the bugs go away when I blacklist the radeon module. Unfortunately I cannot switch off the Radeon-graphics card, when the module for it isn't loaded. :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Driver crash during recovery boot and in normal boot (Regression from 2.6.38-3 to -4) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
