*** This bug is a duplicate of bug 714904 ***
https://bugs.launchpad.net/bugs/714904
** This bug has been marked a duplicate of bug 714904
/etc/network/if-up.d/ifenslave is missing (installed under if-pre-up.d)
* You can subscribe to bug 714904 by following this link:
https://bugs.launchp
I forgot to mention that I'm using the same 1.1.0-15ubuntu2 version from
ifenslave-2.6 than Rob. And my kernel is 2.6.35-25-server #44-Ubuntu
SMP.
The info in /proc/net/bonding/bond0 wasn't actually outdated. There is
some problem setting up the bonding device and it's settings. I had to
take the
Rob, your last post seems to be missing some text.
I've been trying to get bonding to work on Maverick server on amd64 too,
and noticed that the /etc/network/if-up.d/ifenslave is missing even
though it's listed in 'dpkg-query -L ifenslave-2.6'. Like Rob said, it
seems like it's been installed in a
Thank you Michael for a good description, it probably saved me from
ending up with an unbootable system.
I had the same symptoms in Maverick after activating the proposed
repository and installing grub-pc_1.98+20100804-5ubuntu3.1_i386. My
reason to segmentation faults wasn't a PnP wireless modem,
Toobuntu: different kernel versions have different initramfs files.
Check if your working and non-working have the same
conf/conf.d/cryptroot in them.
I find using UUIDs a bit too hard (or at least I'm not used to deal with
them so much), that's why I did my initial fix with /dev/sdaX so that I
wa
That was really the reason, wrong UUID and therefore cryptsetup failed
since it didn't find the correct partition. The first visible error
message "cryptsetup: evms_activate is not available" was kinda
misleading.
So toobuntu and Eric, check that you have correct UUID.
You can check and fix it by
Ehm... Actually my "bug" seems to be a copy&paste mistake made by myself
in crypttab. I didn't remember to change the UUID to match this laptop
when I copied it from a previous install.
--
encrypted block devices unavailable with linux-virtual
https://bugs.launchpad.net/bugs/663053
You received t
I'm getting the "cryptsetup: evms_activate is not available" on boot
too, but I don't think this has anything to do with linux-virtual, since
I don't use it. I have just installed 4 laptops without problems using
the 10.10beta image (i386) in last two weeks, and now with the fifth I
used the final
I didn't have much luck with 0.0+svn966653-0ubuntu0.1. After installing
it from jaunty-proposed (with punch of other updated packages) I:
1. removed my hidden network from the settings (all the old settings was there
from the old install)
2. used the "Connect to hidden network." to add my network
I use my phone to get mobile broadband on my laptop, which means that
the phone is already turned on when I plug it in via USB. So there is no
need for even trying unlocking it, and I've never configured my PIN
anywhere.
That of course doesn't mean that the widget wouldn't try unlocking the
phone,
I got tired of this bug and installed wicd, which removed network-
manager, network-manager-kde and plasma-widget-network-manager from the
system. After the first install wicd wasn't able to connect to a hidden
network (I wasn't able to input the ESSID), but after a reinstall it
works well and auto
This could however be a problem with network-manager-kde (AFAIK to be
able to use Gnome's nm-applet you have to use network-manager-gnome).
When I plug my phone in, I get the following in my daemon.log:
nm-system-settings:SCPlugin-Ifupdown: device added (udi:
/org/freedesktop/Hal/devices
usb
I am able to get mobile broadband working using wvdial, so this rules
out the possibility that the bug would be somewhere deeper in the
system.
--
kubuntu jaunty plasmoid-network-manager can't use mobile broadband
https://bugs.launchpad.net/bugs/334122
You received this bug notification because y
I wasn't able to make knetworkmanager connect automaticly either on my
quick test. Actually I wasn't able to make it to connect at all...
I wonder if this bug is limited to some specific hardware, since it
doesn't seem to affect a lot of people. (Not that I would have any idea
how many people are
** Changed in: plasma-widget-network-manager (Ubuntu)
Status: New => Confirmed
--
kubuntu jaunty plasmoid-network-manager can't use mobile broadband
https://bugs.launchpad.net/bugs/334122
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to pl
If network-manager-gnome works, then I guess this is a bug in network-
manager-kde? And not in the plasma widget. I get these lines in my
daemon.log after logging in and before doing any tricks:
NetworkManager: list_connections_cb(): Couldn't retrieve connections:
No such method 'ListConnection
I also think that the mentioned KDE bug is a different bug. It's about
NetworkManager-kde4 not been able to save (or show) the used password.
My password is saved and I can see it if I check the "Show password"
field. Also, nm-tool doesn't show my network at all. (It does show it
after I do the tri
I haven't got mobile broadband working either by using my mobile phone
and USB cable in Alpha 5. The plasma-widget-network-manager detects the
phone after plugging the phone in by showing (the kinda ugly) black and
white phone image, but it never seems to even try to start connecting.
--
kubuntu
This still happens with the latest release (0.0+svn930811-0ubuntu1).
I managed to get the hidden wireless network working by giving the
system a little hint: from konsole I used iwconfig to set the essid of
my hidden network for the wireless interface, and few moments after that
kwallet pops up an
Public bug reported:
Binary package hint: plasma-widget-network-manager
I installed Jaynty's Alpha4 (Kubuntu) on my laptop for testing + all the
current updates, and I can't connect to a hidden network.
If I put the network visible, the widget connects automaticly as
configured. It keeps working
Theodore: as I said in the mentioned bug #122118 I'm using Gutsy too
without problems with the kernel version 2.6.22-14.52 of linux-
image-2.6.22-14-generic. What's your kernel?
Comments on bug #124406 seem to support my guess that this is a kernel
bug (starting from:
https://bugs.launchpad.net/ub
This bug sounds much like what was reported already in bug #122118. My
best guess is that it's a kernel bug that happens under heavy load. If
that's the case, then it could be that this bug is back in the new
kernels. This can be tested pretty easily if someone can downgrade to
Gutsy's kernel and g
Since my last post a lot has changed on my system. I have a totally
different computer (well, the mouse and keyboard are the same) and I had
to make a fresh install of Gutsy for this machine. I don't have this
problem anymore with this setup, and if I remember correctly, I was able
to get things wo
That's interesting. But (for me at least) it's still happening only for
the mentioned few applications and only when using keyboard shortcuts.
I'd still bet on a bug in some common library. But could different
kernel somehow affect how some library works?
That could be easily tested if I can find
This is still happening for me too in (Kubuntu) Gutsy RC. I just got 52
new firefox windows by pressing Ctrl-N once, and CPU usage was 100%
while it made them... Quite annoying.
** Changed in: firefox (Ubuntu)
Status: Incomplete => Confirmed
--
Pressing Ctrl+W once closes all tabs, one by
Fixed in the latest updates in the Gutsy's RC.
** Changed in: meta-kde (Ubuntu)
Status: New => Fix Released
--
[Gutsy] Konsoles don't group up in KDE's taskbar
https://bugs.launchpad.net/bugs/128303
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
In the latest updates in the RC this is now fixed.
--
[Gutsy] Konsoles don't group up in KDE's taskbar
https://bugs.launchpad.net/bugs/128303
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@
This still happens with the latest updates. I think this bug is very
much confirmed, but due to it's random behaviour it might be hard to
track down. Can you try to reproduce this again Hilario?
--
Pressing Ctrl+W once closes all tabs, one by one
https://bugs.launchpad.net/bugs/122118
You receive
*** This bug is a duplicate of bug 122118 ***
https://bugs.launchpad.net/bugs/122118
** This bug has been marked a duplicate of bug 122118
Pressing Ctrl+W once closes all tabs, one by one
--
key combination ctrl+w to close a tab is repeated automatically
https://bugs.launchpad.net/bugs/13
I don't know if this helps anyone, but I tried to downgrade back to
current Gutsy's version 6.6.193-1ubuntu1, but that version didn't
understand my new dual head setup and I ended up in cloned single
monitor mode. I then went to the 6.7.192-1ubuntu1 from
http://people.ubuntu.com/~bryce/Testing/ati/
I hope you didn't ask that from me Tormod, since I don't even use
Ubuntu. I use Kubuntu. :)
But I found out that it's still possible to have a static setting for
dual head in xorg.conf. Otherwise you'd have to put the xrandr command
somewhere where it's runned after boot for KDM (or GDM). Here's a
Okey... Didn't even know what a zaphod mode was. :/ But I got my dual
head working after little searching and playing around with the configs.
All I had to do was add a "Virtual 2580 1024" to the new single monitor
xorg.conf under Screen section's subsection "Display" and then use
"xrandr --output
This is the log with the new dual head config. Still crashing like the
old one. Note that DefaultDepth was 24 in the new config after the
suggested "dpkg-reconfigure -phigh xserver-xorg".
The new driver (xserver-xorg-video-ati_6.7.192-1ubuntu2_i386.deb) worked
like the previous one when using the
Tormod: could be. Do you think it's related to this bug?
Timo: no luck. Dual head still crashes with xserver-xorg-video-
ati_6.7.192-1ubuntu2_i386.deb from
http://users.tkk.fi/~tjaalton/dpkg/ati
I made a new dual head config after the suggested "dpkg-reconfigure
-phigh xserver-xorg", it's attache
Same here, it didn't fix my problem. The xserver-xorg-video-
ati_6.7.192-1ubuntu1_i386.deb downloaded from
http://people.ubuntu.com/~bryce/Testing/ati/ worked actually even worse
with my dualhead setup: even the left screen connected to DVI was blank.
It seems that X crashed completely with this se
Is anyone else still having problems with this bug? Since this starts to
be quite irritating. Imagine being able to use only the left half of
your desktop...
--
ATI Driver Gets Black Screen on Radeon 7500 Mobile (Regression)
https://bugs.launchpad.net/bugs/132716
You received this bug notificatio
My xinerama setup hasn't worked for awhile because of another bug, but
this still happens with my single screen setup, so it's not related to
xinerama.
Yesterday I pressed Ctrl-N in Firefox and ended up with 100+ new windows
before Firefox crashed... :/
--
Pressing Ctrl+W once closes all tabs, o
This still happens with the latest updates (Tribe 5).
--
[Gutsy] Konsoles don't group up in KDE's taskbar
https://bugs.launchpad.net/bugs/128303
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-bu
I can confirm that my desktop's dualhead setup is still broken with the
latest updates (Tribe 5).
--
ATI Driver Gets Black Screen on Radeon 7500 Mobile (Regression)
https://bugs.launchpad.net/bugs/132716
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
This is my xorg.conf for the dualhead setup. DRI is always disabled by X
itself since it's not working with xinerama. I tried to play around with
the MonitorLayout option, but it didn't make any difference...
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/8893094/xorg.conf
--
Here is my log on dualhead setup from start to KDM's login screen. This
time the login screen was a mess too. The user list wasn't loaded and it
missed other components too... Like said before, the right screen
connected to VGA (called "Extra Screen" in log) is blank. The screen "is
there" though,
Disabling AGPFastWrite didn't fix my dualhead setup. (Tried to disable
it on both devices and also only for the VGA device.) One note: when I
use my original single screen setup, the desktop gets correctly cloned
to both screens.
--
ATI Driver Gets Black Screen on Radeon 7500 Mobile (Regression)
I guess my bug is related to this one. I have a dualhead setup using
Radeon 7500 and my right screen (connected to VGA) went blank after my
todays update in Gutsy, but the left screen (connected to DVI) still
works. Well it actually works when using my single screen setup, since
on dualhead the lef
Should have checked the dependencies more closely before. I've now tried
Gwenview too (has the same problem also), and these are the common packets for
them all:
libc6
libx11-6
libxext6
libxi6
libxinerama1
And yes, I have two screens and I'm using xinerama, but the problem
remains even if I use
I have to correct myself, this bug isn't annoying, it's totally
frustrating.
In GQview you don't even have to be on full screen mode. In normal mode
it comes up when changing images with arrow keys. I also tried QIV, but
it also has the same problem than GQview! Watching the dependencies of
all th
> I forgot to mention that I'm using Kubuntu, but the delay was 660 ms
and speed 25 chars/s. I pushed the delay now to 1200 ms. Let's see if it
helps on this issue...
It did not. GQview was skipping images a moment ago. And this time it
probably had a new record: it skipped about 115 images. :(
T
> How is your keyboard repeat rate setup? Preferences -> Keyboard
> ... and try to push the Delay to "Long"
I forgot to mention that I'm using Kubuntu, but the delay was 660 ms and
speed 25 chars/s. I pushed the delay now to 1200 ms. Let's see if it
helps on this issue...
--
Pressing Ctrl+W once
I have same kind of symptoms on Gutsy (and I'm not using Beryl). But not
only with Ctrl-W, also with Ctrl-T and when using the "search on page as
you type". And Ctrl-W doesn't close all the tabs. I normally have many
of them (like 20) and it closes like 5-10. And this also happens in
GQview. Pressi
Installing openoffice.org-gnome fixes OO for me too, but it doesn't fix
Acrobat Reader...
--
[gutsy]Open Office applications don't start
https://bugs.launchpad.net/bugs/127944
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ub
Same problem here with OO and Acrobat Reader. Should the importance of
this bug be decided by someone?
--
[gutsy]Open Office applications don't start
https://bugs.launchpad.net/bugs/127944
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ub
Public bug reported:
Binary package hint: kde
Multiple Konsole windows don't group up in KDE's taskbar. Multiple
firefox and konqueror windowses work fine and group up...
Running Gutsy with latest updates.
** Affects: meta-kde (Ubuntu)
Importance: Undecided
Status: New
--
[Gutsy
Just one more note: this wasn't a compiz problem, since I don't even
have it installed.
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mai
This happens to me too. Using the latest and greatest Gutsy at the
moment (don't know if this happened in Feisty for me since it's X was
too unstable for some weird reason so I quickly changed to Gutsy).
I'm using xinerama too with my Radeon 7500. On konsole the "kcmshell
displayconfig" crashes wi
I finally got tired of the crashing (three times a day isn't so nice...)
and upgraded to Gutsy last week. So far I haven't had a single crash, so
I guess my problem is fixed in Gutsy.
--
X crash: FontFileCompleteXLFD+0xa1
https://bugs.launchpad.net/bugs/71913
You received this bug notification be
I had the same problem. The udevd was using lot of CPU and writing the
same messages over and over again to kernel.log. Stopping and starting
udevd again worked for the session, but it started doing the same thing
again after a reboot. Removing evms fixed the thing also between
reboots.
(Kernel: 2
"setting back to fix committed, as people are *still* reporting this,
instead of searching for the bug, and that openoffice has ftbfs on i386
at least."
I'd guess quite a lot users are on i386, so the fix isn't released to us
yet. :)
And there seems to be a new bug reporting system on (k)ubuntu w
Public bug reported:
Binary package hint: openoffice.org-common
I upgraded from Feisty to Gutsy yesterday. There was some libcurl4
problem with openoffice.org so it wasn't upgraded at that time. Now that
problem is fixed, but the upgrade fails to this:
Setting up openoffice.org-common (2.2.1-5ub
In my case it's definately not because of Beryl, since I don't have it.
(And I've never even tried it.) And since this crashing seems to happen
on different manufacturers graphics cards I don't think the problem is
in those driversl...
There are two upstream bugs having same kind of backtraces:
h
I tried commenting out the one font row from xorg.conf that Bryce
mentioned, but it didn't help.
This time X just hanged, but sshd was killed (gkrellmd was still running
though). Just before the hang I was trying to close one firefox window.I
was able to login from normal terminals (Ctrl-Alt-F1..)
This bug seems to be duplicate to bug #71913.
--
XServer crash while using firefox (Ubuntu 7.04)
https://bugs.launchpad.net/bugs/108829
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.
I have the same problem now after I've upgraded to Feisty. Didn't have
stability problems with Edgy as the original poster. But then again, I'm
using Kubuntu.
More of my backtraces and other findings can be seen in bug #108829 but
here's my latest backtrace:
Backtrace:
0: /usr/bin/X(xf86SigHandle
Got the shortest backtrace today. I guess I have to try a fresh install,
or Gutsy, or another distribution...
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c5d91]
1: [0xe420]
2: /usr/bin/X(FreeClientResources+0x85) [0x8075e65]
3: /usr/bin/X(CloseDownClient+0x1a8) [0x80863e8]
4: /usr/bin/X
Crashing again. This time I was just launching OpenOffice.org...
I'm pretty sure something (which ain't firefox) is writing something
into a memory position it shouldn't... Does these backtraces help
anyone?
I can see from gkrellm from the other machine that right after X crashes
the system reser
Almost typed your name correctly, sorry...
Just had a crash again, below is now my backtrace from the log. This
time sshd wasn't killed so I was able to start kdm remotely.
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x81) [0x80c5d91]
1: [0xe420]
2: /usr/bin/X(dixChangeGC+0xab5) [0x809b4d5]
3: /u
This is really annoying, sometimes it crashes more than once a day...
It seems that it's not a kernel issue, I tried with an older kernel from
Edgy that I still had: linux-image-2.6.17-11-386 (version
2.6.17.1-11.38), but it still crashed.
Frekrik, are you using Ubuntu or Kubuntu?
--
XServer cr
I have similar symptoms with my Kubuntu 7.04. Didn't have these problems
at all with Edgy. Today I've already had two crashes. I haven't found a
way to reproduce it, but I do have firefox open and last time it crashed
when I was just typing some text in firefox. Before the last time it has
crashed
First of all, sorry for making one of the duplicate bug reports (bug
57227), I guess I didn't search with the correct keywords before posting
it. See that bug report for more information about my GPU which was
affected by this problem.
I didn't get the first warning message shown in the fix docume
*** This bug is a duplicate of bug 57153 ***
The new version 1.0.2-0ubuntu10.4 fixed the problem for me. Thanks for
the fast patch Rodrigo. :)
--
xserver-xorg-core 1.0.2-0ubuntu10.3 missing some device drivers? X doesn't
start: stops to fatal error
https://launchpad.net/bugs/57227
--
ubuntu-b
** Bug 57282 has been marked a duplicate of this bug
--
xorg-server 1:1.0.2-0ubuntu10.3 breaks X: "no screens found"
https://launchpad.net/bugs/57153
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
*** This bug is a duplicate of bug 57153 ***
** This bug has been marked a duplicate of bug 57153
xorg-server 1:1.0.2-0ubuntu10.3 breaks X: "no screens found"
--
After upgrading dapper 22:nd of august, X doesn't start
https://launchpad.net/bugs/57282
--
ubuntu-bugs mailing list
ubuntu-bugs@
Public bug reported:
Binary package hint: xserver-xorg-core
Hi!
I upgraded my Dapper yesterday and got one new file: xserver-xorg-
core_1%3a1.0.2-0ubuntu10.3_i386.deb. After the upgrade my X doesn't
start anymore. My graphics card is:
8<
:01:00.0 VGA compatible controller: ATI Techn
71 matches
Mail list logo
