[Bug 1731646] Re: missing qDebug output when creating QT applications
I upgraded from 17.04 to 17.10 just yesterday and I was affected from the same issue. I'm sorry to say, @mitya57, you intentionally broke the qDebug _default_ behaviour (and Fedora as well). qDebug()'ing something should result in printing in the console output. If there's issues with some applications that result in too much verbose output, should be fixed in those applications, not shutting up the whole QT qDebug. Anyway, this should be warned to the user in some way during the upgrade. just my 2 cents. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731646 Title: missing qDebug output when creating QT applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1731646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 760632] Re: Resizing Konsole crashes the whole system
@Christopher Yes, I have other problems for sure... :( Disabling desktop effect does not solve the problem, I have already tried. I have a Windows installation, but it is inside VirtualBox. I don't have any OS other than Linux. This situation started with a dist-upgrade of a few days ago. As far as I remember, it has only upgraded nvidia-current and xserver-xorg stuff. Before this upgrade all works like a charm, as ever! But it is very very strange that downgrading xorg and nvidia-current doesn't solve the problem. (this is why I'm thinking of an imminent graphics card failure). @Ivan: Nope, I have an old GeForce 8500GT (G86 family). Thks! @All: I think to be off-topic here... Anyway I noticed that some seconds before the system totally crash, the X process goes to 100% of cpu utilization. Then the system becomes totally unresponsiveness, even through ssh. Thanks for your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/760632 Title: Resizing Konsole crashes the whole system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/760632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 760632] Re: Resizing Konsole crashes the whole system
All the workarounds proposed here haven't worked for me. I have had to revert to the nv driver to have a usable system. I tried to downgrade xorg and the binary driver but my system still freeze. I tried (with the current xorg) all the binaries driver from nvidia (270, 275 and the beta 280) and none of them work for me... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/760632 Title: Resizing Konsole crashes the whole system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/760632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 760632] Re: Resizing Konsole crashes the whole system
@Vlada: yes, I have tried both. I have tried the binary directly from nvidia site, not from the repository. Check here: http://www.nvnews.net/vbulletin/showthread.php?t=122606 I was not able to use the nouveau driver due to some kind of libdrm incompatibility... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/760632 Title: Resizing Konsole crashes the whole system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/760632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 760632] Re: Resizing Konsole crashes the whole system
@vlado: I've tried all the binaries available in the repositories, then I've started to try all the binaries from official nvidia releases (the lastest 270, 275 and 280). None of them works. My issue is not strictly related to konsole. The system freezes whenever I have lot of GPU intensive task, ie a lot of transparencies, video player streaming or *flash player* running. With Adobe Flash Player I'm having screen redrawing problem from maverik and natty has not solved it. I'm starting to have the doubt that this may be a the signal of an imminent hardware failure... About nouveau: I have clean my system from all components of other drivers... I'm quite sure the problem isn't this... Thks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/760632 Title: Resizing Konsole crashes the whole system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/760632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 774780] [NEW] Upgrading from Maverik to Natty has replaced mdadm with dmraid, making the system unbootable
Public bug reported: Binary package hint: base-installer I have upgraded from Maverik to Natty, x86_64 Desktop release. After the upgrade, the initramfs was configured to load dmraid drivers instead mdadm driver, making the system fails to boot. I have the following disk configuration: /dev/sda /dev/sda1 - NTFS /dev/sda2 - raid partition (md0 - / - raid 0) /dev/sda3 - ext2 (/boot) /dev/sdb /dev/sdb1 - raid partition (md1 - /home - raid 1) /dev/sdc /dev/sdc1 - NTFS /dev/sdc2 - raid partition (md0 - / - raid 0) /dev/sdc3 - swapfs /dev/sdd /dev/sdd1 - raid partition (md1 - /home - raid 1) Before the upgrade, the system booted from the /dev/sda3 partition and then mounted the md0 partition to continue the boot process. After the upgrade the system was not able to see the mdX partitions, trying to mount a series of dm-X partitions, that made the boot process to fail in the very first stage. I have booted the system with a live Natty x86_64, but I have had the same problem. The live was (and is) not able to see the mdadm partitions. I solved the issue booting with a Maverik live (also Lucid works), that is able to correctly see the mdX partitions after having installed the mdadm package. I have chrooted into the broken installation, purged the dmraid package and forced the re-installation of the mdadm package. Now my upgraded Natty x86_64 is working like a charm :) Please ask me for more information, if needed. Thanks for your great work! Yusef Maali ** Affects: base-installer (Ubuntu) Importance: Undecided Status: New ** Tags: dmraid maverik mdadm natty ubuntu upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/774780 Title: Upgrading from Maverik to Natty has replaced mdadm with dmraid, making the system unbootable -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 591024] Re: Can't edit Auto eth0 connection makes impossible to use static Ip / custom connections in Kubuntu/Kde
Hi Fabio, I'm wondering why you have marked as invalid this bug. It is still present in Kubuntu 10.10... Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/591024 Title: Can't edit Auto eth0 connection makes impossible to use static Ip / custom connections in Kubuntu/Kde -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661654] Re: pam_motd doesn't rename /var/run/motd.new if run-parts exits with errors
Hi Steve, if this behavior is by design, I will anyway suggest to log the error somewhere (syslog?). I have had lost a lot of time figuring out what the matter was. If pam_motd had has logged the error, I would have solved the issue in a fraction of time. Dustin, it isn't cpu-checks related. During the upgrade I lost the update-notifier-common package and, with it, a lot of scripts (included the cpu-checks script). Thanks you all for your great work on Ubuntu! Yusef -- pam_motd doesn't rename /var/run/motd.new if run-parts exits with errors https://bugs.launchpad.net/bugs/661654 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661654] [NEW] pam_motd doesn't rename /var/run/motd.new if run-parts exits with errors
Public bug reported: Binary package hint: libpam-modules ** Problem: pam_motd module creates the file /var/run/motd.new but doesn't rename it into /var/run/motd. The /etc/motd symlink points to /var/run/motd and at each user login are shown old informations. ** Repeatable: Yes, always ** How to repeat: You need to force run-parts /etc/update-motd.d to exit with errors. To complete this task just add in the update-motd.d chain a script that exits with error or a symlink to a script that doesn't exist. ** Explanation: I discover this issue while upgrading from lucid to maverik (server edition). For some reason, the package update-notifier-common was removed and I was full of broken symlinks in the update-motd.d chain. At each ssh login I was presented with stale informations. Looking into the pam_motd.c code I found the problem. The module performs a system(run-parts /etc/update-motd.d /var/run/motd.new) call, that returns a non-zero value if run-parts exits with errors. If the system() call returns a non-zero value, the following rename() call is not executed. The file /var/run/motd.new is *always* created and written to disk with the output of the working scripts. We are in the situation where the /var/run/motd.new is updated but never renamed into /var/run/motd, if some scripts have bugs or exit with errors. I have attached a patch that should solve this problem. The rename() call is not blocked by the system() call and moreover if run-parts exits with a non-zero value, pam_syslog is used to log the error and help sysadmins to find rapidly the problem. Within the patch, the rename() call is always executed, even if run-parts fails totally and /var/run/motd.new is not created. In this case, the rename() call doesn't perform the renaming and returns a non-zero value (but we are not interested in it). Thanks, Yusef ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: motd pam run-parts ssh update-motd.d -- pam_motd doesn't rename /var/run/motd.new if run-parts exits with errors https://bugs.launchpad.net/bugs/661654 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661654] Re: pam_motd doesn't rename /var/run/motd.new if run-parts exits with errors
** Patch added: pam_motd.patch https://bugs.launchpad.net/bugs/661654/+attachment/1696218/+files/pam_motd.patch -- pam_motd doesn't rename /var/run/motd.new if run-parts exits with errors https://bugs.launchpad.net/bugs/661654 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 399071] Re: pam_motd: assume update-motd responsibilities
Hi Dustin, I'm sorry for having written in the wrong place. I have filed the bug right now (#661654) Thanks, Yusef -- pam_motd: assume update-motd responsibilities https://bugs.launchpad.net/bugs/399071 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 399071] Re: pam_motd: assume update-motd responsibilities
Hello, upgrading from lucid to maverik (server edition), for some reason, the package update-notifier-common was removed. As main effect I have pam_motd to not refresh the /var/run/motd file. Looking into the code (mainly the Steve's patch revision) I found the problem. As Steve said: I've also tweaked the first patch slightly, to avoid clobbering /var/run/motd if [...] the run-parts call fails; This is useful, but in my case, I have had a dirty update-motd.d directory, with some scripts exiting with error (ie: run-parts: /etc/update-motd.d/20-cpu-checker exited with return code 2). The system() call returns the error and the file /var/run/motd.new was never renamed into /var/run/motd. Consider that even if some scripts of the update-mod.d chain fail, the file /var/run/motd.new is created and written to disk with the only output of the working scripts. I have attached a patch that should solve this problem (at least I think it is a problem :) ). The rename() call is not blocked by the system() call and moreover if run-parts exits with error (system()!=0) pam_syslog is used to log it and help sysadmins to find rapidly the problem. If run-parts fails totally and /var/run/motd.new is not created, the rename() call returns the error (but we are not interested in it). I hope to be useful. Yusef ** Patch added: pam_motd.patch https://bugs.launchpad.net/ubuntu/+source/pam/+bug/399071/+attachment/1688175/+files/pam_motd.patch -- pam_motd: assume update-motd responsibilities https://bugs.launchpad.net/bugs/399071 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518122] Re: Please rebuild for newer version of ImageMagick
I can't recompile the package so I used the one provided by Marco Cimmino (post #8). It works correctly and it has solved my issue. Just a question for Marco: in your package you have applied the patch in post #6? -- Please rebuild for newer version of ImageMagick https://bugs.launchpad.net/bugs/518122 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 495694] Re: kacpid uses 100% of CPU. Kernel is 2.6.31-17
Same issue. Ubuntu Server, Lucid. Hw: Intel Atom D945GCLF. I haven't powernowd installed. This problem is come after upgrading from 9.10 to 10.04. Before that, I have never seen kacpid work in a such way. ** Tags added: lucid server -- kacpid uses 100% of CPU. Kernel is 2.6.31-17 https://bugs.launchpad.net/bugs/495694 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303068] Re: Static IP ethernet network setting is lost after reboot
I have done some test with Kubuntu 9.10 x86_64 / 10.04 x86 / 10.04 x86_64 inside a VirtualBox environment. The bug is 100% reproducible. Reading your last message, I have noticed that in Kubuntu there isn't a way to edit the Auto Eth0 connection (as you do). It is shown by knetworkmanager and by plasma-widget-networkmanagement as available, but if you go to the Manage Connection panel only the custom connections are shown. The Auto Eth0 is hidden. I have attached a screenshot. After I create my static connection, the Auto eth0 remains alive and I can't de-select the connect automatically item. I suppose it takes priority over the other connections. If this is true (and I think so), the only way to use network-manager in Kubuntu is only through dhcp... This is definitely a Kubuntu/Kde bug, not a network-manager bug. I'm going to open a new bug. ** Attachment added: auto-eth0-missing.png http://launchpadlibrarian.net/49846802/auto-eth0-missing.png -- Static IP ethernet network setting is lost after reboot https://bugs.launchpad.net/bugs/303068 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 591024] [NEW] Can't edit Auto eth0 connection makes impossible to use static Ip / custom connections in Kubuntu/Kde
Public bug reported: I have noticed that in Kubuntu/Kde is not possible to edit the Auto eth0 connection and, more important, is not possible to de-select its Connect automatically item. If I create a custom connection, ie for a static ip configuration, even if I select the Connect automatically item, after each reboot the Auto eth0 profile takes priority over all other custom connections. Seems that Kubuntu/Kde can only use Dhcp configuration at startup. I have tested this issue with a 100% reproducibility in Kubuntu 9.10 and 10.04 both in x86 and x86_64 version. Ubuntu/Gnome doesn't have the problem and allow to edit correctly also the Auto eth0 connection. (see #303068). Thanks for your great work! ** Affects: kdenetwork Importance: Undecided Status: New ** Affects: knetworkmanager Importance: Undecided Status: New ** Affects: plasma-widget-networkmanagement Importance: Undecided Status: New ** Affects: ubuntu Importance: Undecided Status: New ** Also affects: plasma-widget-networkmanagement Importance: Undecided Status: New ** Also affects: knetworkmanager Importance: Undecided Status: New ** Also affects: kdenetwork Importance: Undecided Status: New ** Description changed: I have noticed that in Kubuntu/Kde is not possible to edit the Auto - eth0 connection and, more important, is impossible to de-select its + eth0 connection and, more important, is not possible to de-select its Connect automatically item. - In this way if I create a custom connection, ie for a static ip configuration, even if I select the Connect automatically item, after each reboot the Auto eth0 profile takes priority over all other custom connections. - Seems to be that Kubuntu/Kde can only use Dhcp configuration at start-up. + If I create a custom connection, ie for a static ip configuration, even if I select the Connect automatically item, after each reboot the Auto eth0 profile takes priority over all other custom connections. + Seems that Kubuntu/Kde can only use Dhcp configuration at startup. I have tested this issue with a 100% reproducibility in Kubuntu 9.10 and 10.04 both in x86 and x86_64 version. - Ubuntu/Gnome doesn't report the problem and shows correctly also the Auto eth0 connection. (see #303068). + Ubuntu/Gnome doesn't have the problem and allow to edit correctly also the Auto eth0 connection. (see #303068). Thanks for your great work! -- Can't edit Auto eth0 connection makes impossible to use static Ip / custom connections in Kubuntu/Kde https://bugs.launchpad.net/bugs/591024 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 591024] Re: Can't edit Auto eth0 connection makes impossible to use static Ip / custom connections in Kubuntu/Kde
** Attachment added: auto-eth0-missing.png http://launchpadlibrarian.net/49853610/auto-eth0-missing.png -- Can't edit Auto eth0 connection makes impossible to use static Ip / custom connections in Kubuntu/Kde https://bugs.launchpad.net/bugs/591024 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 303068] Re: Static IP ethernet network setting is lost after reboot
I have filed a new bug report: https://bugs.launchpad.net/bugs/591024 -- Static IP ethernet network setting is lost after reboot https://bugs.launchpad.net/bugs/303068 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 5364] Re: Can't use static ip address with network-manager (and thus no VPN connections menu for static users)
Speaking about Kubuntu and not Ubuntu, I noticed the the Auto Eth0 and its Connect automatically flag is not editable. This makes impossible to create a custom connection (ie for static ip). At each startup the Auto Eth0 takes priority over all other connections. I have filed a bug report about this: https://bugs.launchpad.net/bugs/591024 -- Can't use static ip address with network-manager (and thus no VPN connections menu for static users) https://bugs.launchpad.net/bugs/5364 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 280762] Re: knetworkmanager under kde4 doesn't recognize the static IP connections that I have configured.
Hi Jonathan, I have not understand if knetworkmanger is no longer supported and if it is removed from Kubuntu 9.10 and 10.04. Seems from your words that it is replaced by the plasma-widget-networkmanagement as default option. But if you install a fresh 9.10/10.04 Kubuntu (or update to them) you will found knetworkmanager up and running, not the plasma widget :) Anyway I noticed that the Auto Eth0 connection and its Connect automatically flag is not editable. This makes impossible to create a custom connection (ie for static ip). At each startup the Auto Eth0 takes priority over all other connections. I have filed a bug report about this: https://bugs.launchpad.net/bugs/591024 -- knetworkmanager under kde4 doesn't recognize the static IP connections that I have configured. https://bugs.launchpad.net/bugs/280762 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to knetworkmanager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 315677] [NEW] Wrong dhcp rules for ufw
Public bug reported: In /etc/ufw/before.rules there is the following rule: # allow dhcp client to work -A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT It is wrong. Port 67 is bootps (server side) and port 68 is bootpc (client side). The rule is inserted into ufw-before-input chain, that is part of the INPUT chain, so it is matched against incoming packets. Dhcp incoming packets have as source port bootpc/68 (the client) and as destination port bootps/67 (the server). The above rule should be correct, if it will be inserted into the OUTPUT chain. I provide a simple patch to correct the problem. I'm using Intrepid/8.10 with both Kubuntu and Ubuntu Server and both have this issue. ufw package installed is 0.23.2. Best Regards, Yusef Maali ** Affects: ufw (Ubuntu) Importance: Undecided Status: New -- Wrong dhcp rules for ufw https://bugs.launchpad.net/bugs/315677 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315677] Re: Wrong dhcp rules for ufw
** Attachment added: correct dhcp rule in /etc/ufw/before.rules http://launchpadlibrarian.net/21069227/before.rules.patch -- Wrong dhcp rules for ufw https://bugs.launchpad.net/bugs/315677 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 315677] Re: Wrong dhcp rules for ufw
Please forgive me and close this bug... The rule is correct, I need to sleep... :( The rule, as written in the comment, allow dhcp client to work. My perplexity come from the installation of a dhcp server. It needs the rule in the patch to work correctly. But if you have a dhcp server on a machine that is also a dhcp client (perhaps it has no sense...), you need both rules... Please close this bug as invalid. Regards, Yusef Maali ** Changed in: ufw (Ubuntu) Status: New = Invalid ** Visibility changed to: Private -- Wrong dhcp rules for ufw https://bugs.launchpad.net/bugs/315677 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279186] Re: x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
For the intel board it was a purely Bios issue. Please check if you have an upgrade for your netbook. Otherwise I think you should write to the MSI support, highlighting this bug report. MSI may have to update their Bios's board. Yusef. -- x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2) https://bugs.launchpad.net/bugs/279186 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279186] Re: x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
Robert, in my atom box the patched kernel still doesn't work... I have to admit that I have used no conventional method: I have compiled the kernel with a live 8.10 x86_64 kubuntu on a Core2Duo (and it compiles in less than 5 hours ;) I have booted the atom box with a netboot debian live (because it hasn't a cdrom drive) I have installed the new kernel chrooting inside the broken installation. I get, again, a kernel panic. Anyway, now I will try to compile directly on the atom box, hoping this gives a working kernel... BTW, where I can find an alpha5/6 iso to download? I'm not able to find it on the net... :( Regards, Yusef -- x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2) https://bugs.launchpad.net/bugs/279186 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279186] Re: x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
I have done my test with an Ubuntu Hardy server (8.04.1) x86_64. The new kernel doesn't work... :( I get the same kernel panic... It is behaving in a very strange way, because the third time I've tried to boot, it worked!! After that, only kernel panics. Very very strange... I need to buy a serial cable to log the kernel startup. - Andre: it took exactly 3 hours to compile all the stuff... May you haven't pass CONCURRENCY_LEVEL=2 to make-kpkg? - Robert: if you would like to do more test, just tell me. And if you would like to try the kernel package I have created I can upload them somewhere. Anyway, the only difference I have from a brand new D945GCLF is the bios version I have upgraded to the latest version 0103 (LF94510J.86A.0103.2008.0814.1910). Yusef -- x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2) https://bugs.launchpad.net/bugs/279186 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279186] Re: x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
Robert, thanks for your help! Yes, it is a random pattern... sometimes it boots, sometimes it don't... Also in my case the kernel is around 250Mb, as you suggest I have attached my .config I'm rebuilding with your config file. With a simple diff, I'm not able to see if there are differences between the two configs. Yep, 3 hours and 2 minutes. Of course, a null modem ;) Yusef ** Attachment added: config-2.6.27.4-custom http://launchpadlibrarian.net/19709779/config-2.6.27.4-custom -- x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2) https://bugs.launchpad.net/bugs/279186 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279186] Re: x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
and the git log (~100 lines...) Thanks again. Yusef ** Attachment added: git.log http://launchpadlibrarian.net/19709787/git.log -- x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2) https://bugs.launchpad.net/bugs/279186 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279186] Re: x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
But the config file you have attached, is the one installed with a clean Intrepid x86_64 server edition? I was started from that one. Thanks, Yusef -- x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2) https://bugs.launchpad.net/bugs/279186 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54020] Re: Kernel panic on install on amd64
Please have a look also at bug #279186. It seems to be more specific to Intel D945GCLF(2). -- Kernel panic on install on amd64 https://bugs.launchpad.net/bugs/54020 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54020] Re: Kernel panic on install on amd64
I have just tested also netboot kernel of hardy server and intrepid server (the one inside 20080522ubuntu21 directory). They works correctly; the second needs a acpi=off as kernel parameter otherwise the boot finish with a kernel panic. The other two netboot kernel of intrepid version (20080522ubuntu22 and 20080522ubuntu23) doesn't work. Cheers. Yusef Maali -- Kernel panic on install on amd64 https://bugs.launchpad.net/bugs/54020 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54020] Re: Kernel panic on install on amd64
I'm having a similar problem with the Intel D945GCLF (Atom 230, em64t capable). Trying to boot some amd64 ubuntu (intrepid) distributions (ubuntu dektop/server, server netboot and kubuntu), I get an early kernel panic (it is an hard lock). I have tried a lot of possible kernel parameters: acpi=off, acpi=ht, acpi=noirq, noapic, nolapic, pci=nommconf, irqpoll None of them brings me to complete the boot. With the x86 kernel things work as expected. Moreover I've tried the amd64 debian kernel (the one shipped with the netboot install for etch) and it works! (http://ftp.nl.debian.org/debian/dists/etch/main/installer-amd64/current/images/netboot/netboot.tar.gz) debian kernel works, ubuntu kernel don't. If you need more hardware informations I can take them from an x86 installation, because the x86_64 doesn't boot in any way. Thanks. Yusef Maali -- Kernel panic on install on amd64 https://bugs.launchpad.net/bugs/54020 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 279186] Re: x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2)
I'm not a kernel expert but I'm having the same issue with the little sister of your board, the D945GCLF with the Intel Atom 230 (single core, HT capable). I've tried to install the intrepid x86_64 server edition and: - with the iso, I get an early kernel panic with an hard lock. - with the netboot install I'm able to install the system only with the 20080522ubuntu21 version (passing acpi=off). The other two version, including the current, give always a kernel panic. As said, with that particular version of netboot installer I'm able to install the system, but after the first reboot I get only kernel panics. With x86 kernel I have no problem to install ubuntu and also boot a live cd. If it can be useful, the debian etch netboot install for x86_64 works perfectly (but it have a different kernel version). Thanks. Yusef Maali -- x86_64 kernel oops on boot (dual-core Atom 330 board D945GCLF2) https://bugs.launchpad.net/bugs/279186 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 145268] Re: libtunepimp-dev conflicts libraptor1-dev
I'm still having this problem. I'm on a Kubuntu Hardy 8.04.1, x86 platform. I'm attaching apt-cache results: $: apt-cache show libtunepimp-dev Package: libtunepimp-dev Priority: optional Section: libdevel Installed-Size: 1084 Maintainer: Ubuntu Core Developers [EMAIL PROTECTED] Original-Maintainer: Adam Cécile (Le_Vert) [EMAIL PROTECTED] Architecture: i386 Source: libtunepimp Version: 0.5.3-6ubuntu4 Replaces: libtunepimp2-dev, libtunepimp3-dev Depends: libcurl4-gnutls-dev, libexpat1-dev | libexpat-dev, libflac-dev, libmad0-dev, libmpcdec-dev, libmusicbrainz4-dev | libmusicbrainz-dev, libofa0-dev, libogg-dev, libtag1-dev, libtunepimp5 (= 0.5.3-6ubuntu4), libvorbis-dev, zlib1g-dev Conflicts: libtunepimp2-dev, libtunepimp3-dev Filename: pool/main/libt/libtunepimp/libtunepimp-dev_0.5.3-6ubuntu4_i386.deb Size: 242178 MD5sum: 5d6ea10370564702cee5e59d77f69c83 SHA1: a55cc283c70cd75114d91c44294a89fb5857cb2a SHA256: b41897870ad6f1441c2abac930500297db052fd0d02ab393565014f1ade05910 Description: MusicBrainz tagging library development files Libtunepimp simplifies tagging your audio files with the correct data about artist, album and track title using the MusicBrainz infrastrucure. It works on top of libmusicbrainz and libraries to read audio in FLAC, MP3 Musepack (MPC), Speex, The True Audio (TTA), Ogg Vorbis, WAVE and WMA and WavPack (WV). . This package contains headers, documentation and static libraries. . Homepage: http://musicbrainz.org/doc/libtunepimp Bugs: mailto:[EMAIL PROTECTED] Origin: Ubuntu $: apt-cache show libraptor1-dev Package: libraptor1-dev Priority: optional Section: libdevel Installed-Size: 644 Maintainer: Ubuntu Core Developers [EMAIL PROTECTED] Original-Maintainer: Dave Beckett [EMAIL PROTECTED] Architecture: i386 Source: raptor Version: 1.4.16-1 Provides: libraptor-dev Depends: libraptor1 (= 1.4.16-1), libxml2-dev (= 2.5.10), libcurl4-openssl-dev, libxslt1-dev (= 1.0.18), pkg-config (= 0.18) Recommends: raptor-utils Suggests: libraptor1-doc Conflicts: libraptor-dev, libraptor0 (= 0.9.12-2), libraptor1 (= 1.0.0-4) Filename: pool/main/r/raptor/libraptor1-dev_1.4.16-1_i386.deb Size: 215370 MD5sum: 275a524c137dd3e77f436e80dff89055 SHA1: da3c58bd5a5f1c28cbe74f00cc7d22f52540b1b9 SHA256: 105b3f2344363d63785025d601ac81e20646366a9f78c8b3c34eda08a9826bd4 Description: Raptor RDF parser and serializer development libraries and headers Raptor Resource Description Framework (RDF) parser and serializer development libraries, header files and documentation needed by programs that want to be compiled with Raptor. Bugs: mailto:[EMAIL PROTECTED] Origin: Ubuntu As you can see this conflicts doesn't seem to be resolved. Thanks. -- libtunepimp-dev conflicts libraptor1-dev https://bugs.launchpad.net/bugs/145268 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 225411] Re: [hardy] vim-latexsuite doesn't work
Save the patch somewhere, i.e. /tmp/vim-latexsuite.patch Then: $: cd /usr/share/vim/registry/ $: sudo patch -p0 /tmp/vim-latexsuite.patch Done. vim-latexsuite package has to be already installed. I hope to be helpful :) -- [hardy] vim-latexsuite doesn't work https://bugs.launchpad.net/bugs/225411 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 225411] [NEW] [hardy] vim-latexsuite doesn't work
Public bug reported: Binary package hint: vim-latexsuite After upgrading to Hardy from Gutsy, I've installed vim-latexsuite $: sudo apt-get install vim-latexsuite $: vim-addons install latex-suite $: vim-addons status # Name User Status System Status [SNIP] latex-suite broken removed [SNIP] and obviously the latex-suite isn't working. After a little investigation, I have found the problem to be into: /usr/share/vim/registry/vim-latexsuite.yaml I've attached a patch that make latex-suite working. I'm using: vim-full: 1:7.1-138+1ubuntu3 vim-latexsuite: 20060325-4.1 ** Affects: vim-latexsuite (Ubuntu) Importance: Undecided Status: New -- [hardy] vim-latexsuite doesn't work https://bugs.launchpad.net/bugs/225411 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 225411] Re: [hardy] vim-latexsuite doesn't work
** Attachment added: vim-latexsuite.patch http://launchpadlibrarian.net/14071667/vim-latexsuite.patch -- [hardy] vim-latexsuite doesn't work https://bugs.launchpad.net/bugs/225411 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
