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
** 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.
--
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]
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
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
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
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
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
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
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
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
** 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
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
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
(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
/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
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
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
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
@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
@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
@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
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.
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
** 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
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
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
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
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
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
** 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
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
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
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
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
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
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
37 matches
Mail list logo
