@Jerone: l-b-m has hit proposed; let me know if that fixes the issue.
--
Lenovo Thinkpad X201 T410 W510 not autoswitching to input mic jack in 10.04
https://bugs.launchpad.net/bugs/557742
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just happened again, except this time the machine wasn't idle; I was
editing a file with gvim. Xorg had been running for about two days.
Same message in the Xorg log:
Fatal server error:
Failed to map batchbuffer: Cannot allocate memory
--
[gm45] Xorg crash when idle: Failed to map
Public bug reported:
Binary package hint: xserver-xorg-video-intel
I have had Xorg crash several times while not at the computer, and I
return to find a KDM login prompt. Before the crash, the screen has been
locked, with no screensaver running.
There may have been notifications appearing in
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/49528472/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/49528473/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/49528474/Dependencies.txt
**
Spoke to Jerone off-line, it sounds like the thinkpad_acpi symbol issue
may have been particular to the build (symbol versioning), so l-b-m
*should* be compatible with thinkpad_acpi once it comes out.
Spoke to Stefan, he has an update pending for linux-backports-modules,
which includes ALSA
@Jerone: it hasn't hit -proposed yet, but it's in the linux-backports-
modules repo (git://kernel.ubuntu.com/ubuntu/ubuntu-lucid-lbm.git) if
you want to build test early.
--
Lenovo Thinkpad X201 T410 W510 not autoswitching to input mic jack in 10.04
https://bugs.launchpad.net/bugs/557742
You
Jerone: just to clarify: we can't update l-b-m to use ALSA 1.0.23,
because that will break thinkpad-acpi ?
--
Lenovo Thinkpad X201 T410 W510 not autoswitching to input mic jack in 10.04
https://bugs.launchpad.net/bugs/557742
You received this bug notification because you are a member of Ubuntu
This looks like what we're after:
http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=commitdiff;h=7b2bfdbc0dee5a321b5c02febe157adebd33ab3a
Perhaps we can SRU this and avoid the l-b-m/thinkpad_acpi issue.
--
Lenovo Thinkpad X201 T410 W510 not autoswitching to input mic jack in
OK, we should check to see if a netinstall build with the fix from
#457878 addresses this issue, otherwise I'll look into this further.
--
netinstall image fails to connect to the network
https://bugs.launchpad.net/bugs/541029
You received this bug notification because you are a member of Ubuntu
Just a stab in the dark, but can you try this with the disk plugged in
to an external power source (if you're not doing that already?) it looks
like the FW bus is being reset, and so the SCSI layer is creating
multiple devices when the requests time out.
--
Firewire disks not working under 10.04
Tobin - how are you booting this image? directly from redboot via a HTTP
load?
--
netboot image fails to connect to the network
https://bugs.launchpad.net/bugs/541029
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Looks like this may not be all controllers/disks; seems to work here
with a generic SBP2 disk interface. I've tested with both a OHCI and
PCILynx firewire controller.
Jerone - could you try with a different FW disk, and see if the problem
still occurs? May help to isolate the root cause.
--
So just to make sure I'm understanding this correctly - you're not
netbooting, right?
--
netboot image fails to connect to the network
https://bugs.launchpad.net/bugs/541029
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: linux-fsl-imx51 (Ubuntu Lucid)
Assignee: Bryan Wu (cooloney) = Jeremy Kerr (jk-ozlabs)
--
Suspend no longer works after updating to 2.6.31-605.9 kernel
https://bugs.launchpad.net/bugs/537083
You received this bug notification because you are a member of Ubuntu
Bugs, which
Working on a fix for the update leds driver.
--
Suspend no longer works after updating to 2.6.31-605.9 kernel
https://bugs.launchpad.net/bugs/537083
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
retrieved from the platform drvdata.
This change updates the suspend and resume functions to use the struct
mc13892_led type.
Signed-off-by: Jeremy Kerr jeremy.k...@canonical.com
** Patch added: Fix for suspend resume with imx51 mc13892 leds driver
http://launchpadlibrarian.net/41195366/0001
** Changed in: linux-fsl-imx51 (Ubuntu Lucid)
Status: Fix Released = In Progress
--
Suspend no longer works after updating to 2.6.31-605.9 kernel
https://bugs.launchpad.net/bugs/537083
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Setting a LED trigger event on a babbage board will cause an oops when
that trigger occurs:
echo mmc0 | sudo dd of=/sys/class/leds/pmic_ledsb/trigger
sudo dd if=/dev/mmcblk0 of=/dev/null
The led_classdev's brightness_set function is called from an atomic
context, but the
** Patch added: Patch to use a workqueue for setting LED brightness
http://launchpadlibrarian.net/40124884/0001-leds-mc13892-Use-workqueue-for-setting-LED-brightnes.patch
** Changed in: linux-fsl-imx51 (Ubuntu)
Assignee: (unassigned) = Bryan Wu (cooloney)
--
mc13892 LED driver oopses
The attached patch does a bit of rework to enable the driver to use a
workqueue. If we need a less intrusive (but more hacky) patch, let me
know.
--
mc13892 LED driver oopses on trigger action
https://bugs.launchpad.net/bugs/531696
You received this bug notification because you are a member of
Jonathan: just to clarify, you're not using launchpad to track any non-
packaging bugs?
** Bug watch added: KDE Bug Tracking System #213962
http://bugs.kde.org/show_bug.cgi?id=213962
** Also affects: kdebase via
http://bugs.kde.org/show_bug.cgi?id=213962
Importance: Unknown
I've done a test build with the patch listed above. PPA details are at:
https://launchpad.net/~jk-ozlabs/+archive/vim
Fixes the bug for me.
--
gvim complains about gtk_form_set_static_gravity: assertion
`static_gravity_supported' failed in the shell it's started from
Attached a new testcase. Rather than use the libc pselect() wrapper, the
new testcase has its own wrapper for pselect.
Compile with:
gcc -o childspin -DUSE_PSELECT_WRAPPER -Wall childspin.c
Running this on a patched kernel (from Amit's comment 16), the program
does not show the blocking
Marking as invalid according to title change
** Changed in: linux (Ubuntu)
Status: New = Invalid
--
Bug Posted In Error - Disregard
https://bugs.launchpad.net/bugs/442697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: kdebase-workspace
If I update the system timezone with:
sudo dpkg-reconfigure tzdata
Then the time shown by the plasma clock widget does not update, but
instead continues showing the previous system timezone.
This used to work; the clock would detect
Just as an additional data point: could you try mounting with the
noserverino option, and let us know if that fixes the problem?
--
2.6.31 - Can't see files in CIFS-mounted directories
https://bugs.launchpad.net/bugs/406466
You received this bug notification because you are a member of Ubuntu
Chasing up with some samba folks, will report back with any answers.
Will also see if I can get a wireshark dissector that understands the
SMB_FIND_FILE_ID_FULL_DIR_INFO responses.
In the meantime, we have a small workaround.
--
2.6.31 - Can't see files in CIFS-mounted directories
sahlberg1 tridge, jkthat packet in the trace is infolevel 105BUT it
is encoded exactly the same as info level 104 (BOTH DIRECTORY Info), i.e. there
is no new field here.
sahlberg1 tridge, jk,this is either 0x104 and 0x105 are identicalor a
bug in the implementation in the
Steve - Ronnie Sahlberg has just coded up a dissector for this (possibly
broken) packet format, want me to put him in touch with you?
--
2.6.31 - Can't see files in CIFS-mounted directories
https://bugs.launchpad.net/bugs/406466
You received this bug notification because you are a member of
Just as an additional data point: could you try mounting with the
noserverino option, and let us know if that fixes the problem?
--
2.6.31 - Can't see files in CIFS-mounted directories
https://bugs.launchpad.net/bugs/406466
You received this bug notification because you are a member of Ubuntu
Chasing up with some samba folks, will report back with any answers.
Will also see if I can get a wireshark dissector that understands the
SMB_FIND_FILE_ID_FULL_DIR_INFO responses.
In the meantime, we have a small workaround.
--
2.6.31 - Can't see files in CIFS-mounted directories
sahlberg1 tridge, jkthat packet in the trace is infolevel 105BUT it
is encoded exactly the same as info level 104 (BOTH DIRECTORY Info), i.e. there
is no new field here.
sahlberg1 tridge, jk,this is either 0x104 and 0x105 are identicalor a
bug in the implementation in the
Steve - Ronnie Sahlberg has just coded up a dissector for this (possibly
broken) packet format, want me to put him in touch with you?
--
2.6.31 - Can't see files in CIFS-mounted directories
https://bugs.launchpad.net/bugs/406466
You received this bug notification because you are a member of
Oliver: My changes should only affect the probe code, so I'd be
surprised if we seen any difference with the rx/tx paths.
However, I've been surprised before, so I've done a baseline build,
version jk0:
http://kernel.ubuntu.com/~jk/bugs/438687/linux-
OK, thanks for the testing. Patch coming.
--
FEC driver does not set DRIVER property in udev which makes network-manager
fail
https://bugs.launchpad.net/bugs/438687
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
. However, this is no different from the existing driver.
Signed-off-by: Jeremy Kerr jeremy.k...@canonical.com
** Attachment added: Patch to convert fec to a platform bus driver
http://launchpadlibrarian.net/33294649/0001-drivers-net-fec-Convert-to-a-platform-bus-driver.patch
--
FEC driver does
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
Status: In Progress = Won't Fix
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
Status: Won't Fix = In Progress
--
FEC driver does not set DRIVER property in udev which makes network-manager
fail
https://bugs.launchpad.net/bugs/438687
Loïc: the updated driver uses the 'platform' bus rather than 'virtual',
so the device has moved in sysfs. Is this going to be a problem?
Also, could you see if NM works as it does for Paul? It's possible that
the DRIVER property is being exposed through a different node in sysfs.
Try a recursive
New test kernel up at http://kernel.ubuntu.com/~jk/bugs/438687/ - the
jk2 version is my most recent build. This has a minimal platform_device
for the FEC driver. We may need to provide more details to the core
driver code, but try this one to see how it goes.
Loïc: try this and let me know how it
New kernel is up (jk3). Let me know how that goes, and thanks for the
continued testing.
--
FEC driver does not set DRIVER property in udev which makes network-manager
fail
https://bugs.launchpad.net/bugs/438687
You received this bug notification because you are a member of Ubuntu
Bugs, which
Looks like the struct netdevice for the fec interfaces don't have a
parent, and hence no driver. I'm currently building a test kernel to
add a parent device for the interface, will let you know how that goes.
** Changed in: linux-fsl-imx51 (Ubuntu Karmic)
Status: Triaged = Won't Fix
**
I'm in the process of adding some minimal platform_driver infrastructure
to the fec code; this should give the appropriate entries in sysfs. Will
report back with a patch tomorrow.
--
FEC driver does not set DRIVER property in udev which makes network-manager
fail
From looking at the udev code, it would seem that this is due to a
missing driver symlink in the sysfs directory for this device. Could you
confirm by pasting the output of:
ls -l /sys/class/net/eth0/device/
?
--
FEC driver does not set DRIVER property in udev which makes network-manager
fail
Paul: any update on this? how has the test kernel been going?
--
Oops randomly with Huawei E220 3G dongle (regression)
https://bugs.launchpad.net/bugs/430011
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Scott: seeing as we're almost at karmic now, I don't think this is
really an issue any more. OK to close?
--
Kopete package is missing .desktop file for meanwhile protocol
https://bugs.launchpad.net/bugs/333041
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Scott: seeing as we're almost at karmic now, I don't think this is
really an issue any more. OK to close?
--
Kopete package is missing .desktop file for meanwhile protocol
https://bugs.launchpad.net/bugs/333041
You received this bug notification because you are a member of Ubuntu
Bugs, which is
EddieVedderIsKing - we'll probably need a little more information to see
what's going wrong here.
Could you reproduce the problem (by plugging in the iPod, and waiting
for the device to appear and disappear), and then attach copies of
/var/log/daemon.log, /var/log/messages and /var/log/syslog?
picolex: looks like you do have permissions to access the device. Are
you seeing the exact same output as Craig Gilding (from comment #6) when
you run gstreamer-properties?
Craig: could you post your output from 'id' and 'ls -l /dev/video0' too?
--
Web cam won't work in Intrepid, worked in
Looks like the glibc syscall wrapper is getting in the way here; the
test run in my previous comment was still using select() even though
pselect is available. Once I get hold of some hardware, will do some
hacking with the wrapper components.
--
ARM architecture lacks support for pselect() and
pixolex: how about the output of 'id'? are you in the 'video' group?
Cheers,
Jeremy
--
Web cam won't work in Intrepid, worked in previous Ubuntu versions
https://bugs.launchpad.net/bugs/303755
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Just tried the attached build, and the childspin example still hangs.
However, it looks like it's waiting somewhere in do_exit, rather than
the previous deadlock, which seems to be waiting in
poll_schedule_timeout
Will see if I can find more about what's happening here.
--
ARM architecture
Does this problem still occur if you add 'nomodeset' to the kernel boot
arguments?
Could be related to #425165.
--
Display turned off during boot.
https://bugs.launchpad.net/bugs/430483
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like the video device is present, but you don't have permission to
open it. Could you paste the output of:
id
ls -l /dev/video0
Cheers,
Jeremy
--
Web cam won't work in Intrepid, worked in previous Ubuntu versions
https://bugs.launchpad.net/bugs/303755
You received this bug notification
Public bug reported:
Binary package hint: qemu-kvm
The qemu-kvm pacakge contains a broken symlink:
[...@b1 ~]$ ls -l /usr/share/kvm
lrwxrwxrwx 1 root root 8 2009-09-10 10:49 /usr/share/kvm - qemu-kvm
The /usr/share/qemu-kvm directory does not exist. This means that
packages
Public bug reported:
Binary package hint: qemu-kvm
The qemu-kvm pacakge contains a broken symlink:
[...@b1 ~]$ ls -l /usr/share/kvm
lrwxrwxrwx 1 root root 8 2009-09-10 10:49 /usr/share/kvm - qemu-kvm
The /usr/share/qemu-kvm directory does not exist. This means that
packages
Patch is now in udev:
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=d412a685736e3b3350b555f4d7d8ebfc80aa54c9
--
sshd zombie processes and strange behavior after karmic upgrade
https://bugs.launchpad.net/bugs/407428
You received this bug notification because you are a member of
Looks like this patch has been accepted to udev:
http://www.spinics.net/lists/hotplug/msg02675.html
The udev.git tree doesn't look like it has been updated though, I assume
Kay hasn't pushed recent changes yet.
--
sshd zombie processes and strange behavior after karmic upgrade
as SIGCHLD is blocked).
This change saves the original sigmask when udev starts, and restores it
just before we exec() the external command.
Signed-off-by: Jeremy Kerr j...@ozlabs.org
I'm not a udev hacker, so not sure if this is the proper fix. I've sent
it to linux-hotplug for comment.
** Attachment
Had a bit of time to look into this, hope this helps:
BUG: unable to handle kernel NULL pointer dereference at 0220
IP: [8112efd0] touch_atime+0x20/0x150
8102efb0 touch_atime:
8112efb0: 55 push %rbp
8112efb1: 48 89 e5
*** This bug is a duplicate of bug 387073 ***
https://bugs.launchpad.net/bugs/387073
** This bug has been marked a duplicate of bug 387073
BUG: unable to handle kernel NULL pointer dereference at 0228
--
plasma-desktop crashes sometimes using ecryptfs home directory
I get the same oops here, usually triggered by plasma-desktop (causes
KDE4 desktop, panel widgets to disappear). Workaround is to restart
plasma desktop.
Linux pororo 2.6.31-9-generic #29-Ubuntu SMP Sun Aug 30 17:39:26 UTC
2009 x86_64 GNU/Linux
I have a dmesg log saved, happy to attach if it'll
Happy to help out from the petitboot side where possible here. One of
the main issues with building petitboot is that it requires a minimal
linux ramdisk for the first-stage boot, which isn't trivial to compile
from scratch (we actually use openWRT as a base for the current builds
on the PB site).
Makes sense, closing.
** Changed in: glibc (Ubuntu)
Status: New = Invalid
--
pthread manpages missing
https://bugs.launchpad.net/bugs/340265
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I just did some experimentation to reduce kwin-induced wakeups.
Initially, I was seeing around 50-60 wakeups per sec due to kwin. By
turning off the 'Track Mouse' effect, I now see around 11 per sec.
Using jaunty here, with uxa accelleration.
--
powertop shows kwin generating lots of wakeups
Public bug reported:
The python2.6-doc package seems to have not generated the standard
library reference. This is the section of the doc that I tend to refer
to the most. Compare:
/usr/share/doc/python2.6/html/library/index.html
with:
http://docs.python.org/library/
Both have the text:
OK, I've gone through the same tests here:
* Just commenting-out autospawn = yes is not enough, as it seems this
is the default. I need to change it to = no for autospawn to actually
be disabled.
* After killing the pulseaudio daemon, Amarok is opening the sound
device directly:
[...@pingu
I'm not too familiar with the phonon/pulseaudio infrastructure, but
happy to help out with chasing this down. Catch me on IRC ('jk-' on
freenode or oftc) if you need any tracing done.
--
[Jaunty] Amarok 2.0.1 will not resume playback after paused
https://bugs.launchpad.net/bugs/330797
You
After the updates to jaunty, all looks good here - no more crashing
plasma.
Thanks for all the work, you guys rock.
--
[jaunty] plasma crashes on start with SIGSEGV
https://bugs.launchpad.net/bugs/338205
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Same behaviour here - Amarok will not resume after pausing, and
occasionally stops playing when changing to the next track.
The UI indicates that Amarok is still in 'play' mode, but the track
position bar does not progress.
In this state, Amarok can not be quit, and needs to be manually killed.
Potential upstream bug no: 179388
--
[Jaunty] Amarok 2.0.1 will not resume playback after paused
https://bugs.launchpad.net/bugs/330797
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Running krandrtray doesn't work for me - just tried this, and plasma
still crashes. I still need to edit the geometry settings manually.
I've shortened the process by keeping a 'clean' plasma-appletsrc file
for each possible monitor configuration (3: work, home, and laptop-only
modes). When the
OK, Interesting. I had 0,0 as the config parameter for Separator
AgendaView, so looks like this change won't affect my setup here -
sizes.count() would return 2, so we'd get the unpatched behaviour
regardless.
Workaround is simple though, I just put sensible values in there instead
(in my case,
Public bug reported:
Using jaunty alpha packages (version shown below), the pthread_create
manpage appears to be missing:
[...@pingu ~]$ man pthread_create
No manual entry for pthread_create
The glibc-doc package still contains some pthread manpages, but not all.
The list of manpages that seem
Public bug reported:
Binary package hint: korganizer
Using jaunty packages here (version listed below) When I open an 'agenda
view' in korganizer (ie, day view or week view), the area where the
calendar should be is completely blank.
Screenshot attached (however, there seems to be an additional
** Attachment added: blank agenda view screenshot
http://launchpadlibrarian.net/23685656/korganizer-screenshot.png
--
Agenda views are completely blank
https://bugs.launchpad.net/bugs/340280
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm seeing the same corrupted graphics and gui slowness, but am using
the intel video driver. Perhaps this is a general kdeui or qt bug?
[...@pingu ~]$ apt-cache policy xserver-xorg-video-intel kdelibs5 libqt4-core
xorg
Is the status for this bug really fix commited/fix released? The fix may
have been comitted/released upstream, but (from the above comments) it
sounds like it's not going to be included in jaunty.
Given that the kde 4.2.2 release is scheduled for after the jaunty
release, we won't see the fix in
Hopefully hotplugging a larger screen then removing it doesn't write
any larger values to this file, otherwise it'll keep crashing...
Unfortunately, after adding an external monitor then removing it, the
geometry settings in plasma-appletsrc are changed back to a crashing
state. This means that
Will this fix be ported to jaunty? KDE is pretty much unusable without
plasma (no system tray = no network manager = no network).
--
[jaunty] plasma crashes on start with SIGSEGV
https://bugs.launchpad.net/bugs/338205
You received this bug notification because you are a member of Kubuntu
Bugs,
Looks good, all working here.
Thanks!
--
Konqueror crashes on startup (when loading about page)
https://bugs.launchpad.net/bugs/336057
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in ubuntu.
--
kubuntu-bugs mailing list
The workaround mentioned in the linked KDE bug does not work, even after
removing ~/.kde/share/config/plasma-appletsrc, plasma still crashes.
This is due to the global plasma-appletsrc file /usr/share/kubuntu-
default-settings/kde4-profile/default/share/config/plasma-appletsrc,
from the
Workaround is to remove all 'geometry=' lines from /usr/share/kubuntu-
default-settings/kde4-profile/default/share/config/plasma-appletsrc, and
~/.kde/share/config/plasma-appletsrc if present.
Nope, doesn't work either. will try messing around with geometry
settings until something works...
ok, to work around this, I needed to find each geometry setting in my
plasma-appletsrc, and manually clip each value to within the screen
size.
Hopefully hotplugging a larger screen then removing it doesn't write any
larger values to this file, otherwise it'll keep crashing...
--
[jaunty]
Public bug reported:
Binary package hint: kdebase-plasma
When I log in via kdm, my KDE session does not have a panel or
background.
This has started happening since today's upgrades. Versions are listed
below.
If I try to manually run plasma from the shell, I get a lot of print
output from
Running under gdb doesn't seem to catch the SEGV, perhaps because plasma
forks and detaches from the parent process and/or kcrash is catching the
signal?
(gdb) run
[ lines omitted ]
plasma(30010) NetworkManagerApplet::showVpn: SHOWING
KCrash: Application 'plasma'
OK, got a backtrace:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb4c79710 (LWP 14855)]
0xb663ceba in QTimer::stop () from /usr/lib/libQtCore.so.4
(gdb) bt
#0 0xb663ceba in QTimer::stop () from
If I remove the plasma-appletsrc file, the crash still occurs - no
widgets added.
--
[jaunty] plasma crashes on start with SIGSEGV
https://bugs.launchpad.net/bugs/338205
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in
Public bug reported:
Using konqueror 4:4.2.0-0ubuntu3 from the jaunty beta here. When I start
konqueror from the KDE menu, a key shortcut, or form the command line,
nothing happens.
Running under gdb reports a SIGSEGV:
(gdb) run
Looks to be fixed in jaunty, gvim starts fine.
vim-gtk: 2:7.2.079-1ubuntu1
gtk-qt-engine: 1:1.1+svn20080816-0ubuntu6
--
gvim hangs on start with gtk-qt-engine-kde4 and qt4 style
https://bugs.launchpad.net/bugs/270972
You received this bug notification because you are a member of Kubuntu
Bugs,
Public bug reported:
Binary package hint: kopete
The kopete package in the Jaunty alpha is missing the following file:
/usr/share/kde4/services/kopete_meanwhile.desktop
This package is included in the upstream kopete install, but it looks
like the deb build is missing the file.
Without this
OK, looks like I had the wrong package - this bug is only applicable to
the kbuntu-experimental PPA, and not the main Januty repo. Feel free to
close.
Also, where is this embedded readme? Those instructions are way out of
date (the icons and desktop file are installed during 'make install'),
and
Found it at kopete/protocols/meanwhile/README. I'll update the info
accordingly.
--
Kopete package is missing .desktop file for meanwhile protocol
https://bugs.launchpad.net/bugs/333041
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kopete in
Public bug reported:
After doing an upgrade today (bringing konsole to
4:4.1.3-0ubuntu1~intrepid1), my konsole sessions no longer respect the
'Show Menubar' setting on start.
I have konsole configured to hide the menubar by default. When I start a
new konsole session, the menubar is always
Upstream KDE bug 172142, looks like a stale settings problem. Opening
the profile settings, enabling and disabling the 'Show menu bar on new
windows' option, and hitting 'Apply' Fixed the problem for me.
--
konsole doesn't respect 'show menubar' setting
https://bugs.launchpad.net/bugs/308473
You
Looks to be fixed in 4:4.1.3-0ubuntu1~intrepid1 due to the new upstream
version.
--
konqueror looses connection to klauncher
https://bugs.launchpad.net/bugs/295329
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in ubuntu.
--
OK, all committed now, so kdenetwork SVN should have meanwhile support.
Revisions r885903 to r885908 contain the meanwhile updates.
Ubuntu packaging folks: feel free to get in touch if you need a hand
with this.
--
Kopete KDE4 doesn't support sametime (meanwhile) protocol
Public bug reported:
I'm trying to build the kopete tree from the SVN tree, to do some
general kopete development work.
However due to an incorrect dependency in the cmake files from the
kdelibs5 package, the build fails:
make[2]: *** No rule to make target
Same problem here. Another sympton is that konqueror keeps prompting to
restore a crash session.
These problems have been reported in kde bugs 167667 and 164307.
Looks like this has been fixed in KDE SVN, commit r870787. Could the
kubuntu team backport this change to the kdebase package?
I have a series of patches to update the kopete meanwhile plugin in
KDE4, which will be committed to KDE svn soon. Once these are in, the
kubuntu folks will need to enable the meanwhile plugin for this to work.
In the meantime, I've ported these over to the intrepid kopete source:
But I couldn't create directories below it (as described in Arnd's
arcticle [1]) even as root. However I need to go back and revisit
this later as I may have made an error somewhere.
You won't be able to mkdir in the spufs mount point - only the
spu_create system call will be able to create
201 - 300 of 319 matches
Mail list logo
