Here is the text that goes with #4:
MarkDelete python-minimal:amd64 < 2.7.15~rc1-1 @ii mK > FU=1
MarkDelete libpython-dev:amd64 < 2.7.15~rc1-1 @ii gK > FU=1
MarkDelete libpython-stdlib:amd64 < 2.7.15~rc1-1 @ii mK > FU=1
MarkInstall python-is-python2:amd64 < none -> 2.7.17-4 @un umN Ib >
I have the same problem but "Starting pkgProblemResolver with broken
count: 1" has a count of 2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898497
Title:
upgrade to "20.04" crashes due to:
Bashar -
Thank you! Your 'fix' worked for me on Kubuntu 14.10 (KDE 4.14.2) kernel
3.16.0-31-generic. This issue had me stumped for months. Very happy to
have everything working now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: apt.log
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+attachment/4251642/+files/apt.log
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
From reply #13:
According to SteveRiley, on the Kubuntu Forum, if you enable All users
may connect to this network in the settings, then the connection does
autoconnect. I tried this once or twice with my wifi networks and it
seems to work.
/var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log
attached.
** Attachment added: main.log
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+attachment/4251641/+files/main.log
--
You received this bug notification because you are a member of Ubuntu
Bugs,
/var/log/upstart/networking.log attached.
** Attachment added: networking.log
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+attachment/4251653/+files/networking.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: network-manager.log
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+attachment/4251655/+files/network-manager.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: network-interface-lo.log
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+attachment/4251654/+files/network-interface-lo.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
SOLVED!!!
The hint to the solution was the content of networking.log:
run-parts: failed to exec /etc/network/if-up.d/static-routes: Exec format error
run-parts: /etc/network/if-up.d/static-routes exited with return code 1
Failed to bring up lo.
run-parts: failed to exec
Public bug reported:
As of June 27th the Flickr API will require SSL to be used for all API
calls. The default URLs in the libflickr-api-perl should be updated to
ensure the library works after this date.
http://code.flickr.net/2014/04/30/flickr-api-going-ssl-only-on-june-
27th-2014/
**
As of today, April 8, 2014, having dist-upgraded, I am able to use
OpenGL 2.0 without crashing KWin on kernel 3.13.0-23. The following
packages were updated on my 64-bit OS:
The following packages will be upgraded:
akonadi-backend-mysql akonadi-server baloo cups-browsed cups-filters
The 'solution' offered in Bug #1299499 worked, permitting my use of
OpenGL 2.0 or 1.2 again, although 3.0 still crashes KWin.
I don't know if the precurser cause of my reported bug was mesa and
libxkbcommon0 incompatibility with kernel's above 3.13.0-19, but adding
the PPA and updating /
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067005/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067007/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
apport information
** Tags added: apport-collected
** Description changed:
On my 64-bit installation, setting OpenGL 1.2, 2.0, or 3.1 when using
kernel 3.13.0-21 causes KWin to crash. I'm forced to use XRender
instead.
This is also occurs using kernel 3.13.0-20.
OpenGL 1.2 and
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067006/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
OpenGL
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067011/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067014/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067012/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067013/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067010/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067009/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067008/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067032/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
apport information
** Attachment added: IwConfig.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067030/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067041/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067017/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067027/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067015/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067040/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067031/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067029/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067016/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
apport information
** Attachment added: AlsaInfo.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067026/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067042/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067034/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067033/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067037/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Well, better more than less?! Looks like I updated this report twice
today. The additions are while I am running on the 3.13.0-19-generic
kernel with OpenGL 2.0 selected (and working properly).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067018/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
apport information
** Attachment added: CRDA.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067028/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
OpenGL
apport information
** Attachment added: RfKill.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067039/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067036/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067038/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
apport information
** Attachment added: WifiSyslog.txt
https://bugs.launchpad.net/bugs/1301570/+attachment/4067019/+files/WifiSyslog.txt
** Description changed:
On my 64-bit installation, setting OpenGL 1.2, 2.0, or 3.1 when using
kernel 3.13.0-21 causes KWin to crash. I'm forced to use
The attached files generated while running the 3.13.0-21 kernel, using
XRender. If needed, I'll change from XRender to OpenGL, generating the
KWin crash, and run ubuntu-bug linux.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On my 64-bit installation, setting OpenGL 1.2, 2.0, or 3.1 when using
kernel 3.13.0-21 causes KWin to crash. I'm forced to use XRender
instead.
This is also occurs using kernel 3.13.0-20.
OpenGL 1.2 and 2.0 works fine and does not crash KWin when using kernel
3.13.0-19.
On
Hmm. Guess that isn't possible. Once the crash occurs, the system
reverts back to XRender.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
OpenGL crashes KWin with 3.13.0-21 kernel
To
On Wednesday, April 02, 2014 08:22:28 PM you wrote:
Do you recall the last kernel version that did not exhibit this bug? We
can perform a kernel bisect if we can identify the last good kernel and
the first bad kernel.
** Changed in: linux (Ubuntu)
Importance: Undecided = High
**
** Description changed:
On my 64-bit installation, setting OpenGL 1.2, 2.0, or 3.1 when using
kernel 3.13.0-21 causes KWin to crash. I'm forced to use XRender
instead.
This is also occurs using kernel 3.13.0-20.
OpenGL 1.2 and 2.0 works fine and does not crash KWin when using
** Summary changed:
- OpenGL crashes KWin with 3.13.0-21 kernel
+ OpenGL crashes KWin with 64-bit 3.13.0-21 kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301570
Title:
OpenGL crashes KWin
Kubuntu: 14.04
KDE: 4.12.95
Kernel: 3.13.0-20-generic x86_64
With this kernel, using OpenGL 1.2, 2.0, or 3.1 crashes KWin.
If I use kernel 3.13.0-19-generic x86_64, I can use OpenGL 1.2 and 2.0
without any problems; KWin does not crash.
--
You received this bug notification because you are a
This 'bug' also affects me. Kubuntu 13.10 64-bit, kernel
3.11.0-13-generic, KDE 4.11.2.
The problem, as I see it, is that the files:
org.freedesktop.upower.hibernate
org.freedesktop.login1.hibernate
don't exist in /usr/share/polkit-1/actions/ and in fact, don't exist
anywhere on my laptop, so
Nope. I get Grub and KDM login. Once logged in to KDM, my desktop is
empty -- it doesn't repopulate as I had it when I hibernated. What is
interesting though, is that launching my browser (Chromium) it reports
that it wasn't closed properly and do I want to restore the session. I
ignore the
Tried Joseph's suggestion. Still receive the error. Ongoing for over a
month now. Have flushed the temporaries as well to no avail. I get
notification New version of Kubuntu available. Run updater, get error,
advised to restart. Restart, get adivsed of new version of Kubuntu, and
reiterate.
This 'bug' is also present in Kubuntu 13.04 (raring) running KDE 4.10.3
as well (my current main OS).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1153064
Title:
Quassel IRC client has a 2 pixel
Public bug reported:
Quassel Version: v0.8.0 (dist-5988f4c)
Protocol version: 10
Built: Mar 20 2012 23:03:20
OS: Kubuntu Precise 12.04.2 LTS (64-bit)
When Quassel is launched it does not position the main window at the
correct screen position even though MainWinPos=@Point(0 0) is initially
set
Kubuntu Oneiric 11.10
Kernel: 3.0.0-12-generic x86_64 (64 bit)
Desktop KDE 4.7.1
Affects me also. Changing the Tooltip Background color in System
Settings Application Appearance Colours Colours to something other
than Black (a lighter color) works. What one cannot change however, is
the color
I can confirm that the temporary workaround provided by Graham Waugh in
#4 above works. Before I made the change to the LangCache.py file,
accessing System Settings Locale System Languages would result in an
error about a KCModule. Closing System Languages then resulted in a
crash of System
Addendum:
Kubuntu 11.10 64-bit
KDE 4.7.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/861930
Title:
systemsettings crashed with AttributeError in __init__(): 'module'
object has no attribute
Status Invalid!! Based on what?
This is a bug - it is valid. I happens here on my NN 32-bit, KDE 4.6.2,
fully updated. KPackagekit and Muon both won't open the Software Sources
for editing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It seems like this problem has become a lot more frequent (happens many
times per day) with the upgrade to Ubuntu 10.10. On 10.04 the problem
also existed, but only happened once every week or so. No changes have
been made to the e-mail setup other than the Ubuntu upgrade.
--
Evolution hangs
This comment from bcooksley, KDE Community Forums Administrator:
I believe this was due to changes in upstream libpolkit policy. I would
suggest filing a critical bug with your distribution, as the system
should be automatically configured out of the box to permit devices to
be connected, mounted
Tim -
Here's the output of the five commands you wanted run:
sudo /usr/lib/cups/backend/usb
nothing returned
sudo usb_printerid /dev/usb/lp0
GET_DEVICE_ID string:
6�
sudo usb_printerid /dev/usb/lp1
nothing returned
lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004
On Monday, May 03, 2010 10:58:42 am you wrote:
Thomas, your problem is the same as Ian's, the device ID of your
printer
has a newline character. For this problem we already have a fix.
Paul L, your problem is the same as Carlos', your printer does not
return any device ID and so the CUPS
On Monday, May 03, 2010 11:26:58 am you wrote:
Paul L, can you actually do so, booting into Jaunty and run the five
commands? This would be really great.
Yes. I'll do that shortly.
Thank you! If you can figure this out, and get our USB printers seen and
configurable again, that would
Tim -
From Kubuntu Jaunty 9.04, KDE 4.3.2.
Here's the output of the five commands you wanted run:
sudo /usr/lib/cups/backend/usb
nothing returned
sudo usb_printerid /dev/usb/lp0
GET_DEVICE_ID string:
�|((��
b���ℷb���R��b���'��p=DB�e��88�p��b��b��c��U�a���a���
Additional info, from my Jaunty OS:
p...@myotherbrain:/var/log$ cat dmesg | grep directional
[ 19.270813] usblp0: USB Bidirectional printer dev 2 if 0 alt 1 proto 2 vid
0x1309 pid 0xF002
--
Cups on Ubuntu Karmic does not recognize USB printer
https://bugs.launchpad.net/bugs/468701
You
On Monday 03 May 2010 01:20:21 pm Till Kamppeter wrote:
Paul L, I see, HAL and its CUPS backend were working around the problem
that your printer does not return a usable device ID. HAL is deprecated
now and therefore the hal CUPS backend is no part of Ubuntu any more. If
your Panasonic
Tim, your a God send! You're recommendation worked!! I have my printer
again!!!
I set it up in CUPS as follows:
Administration Add Printer Local Printer HP Printer (HPLIP)
Connection: parallel:/dev/usb/lp0
Gave it a name, description, and location and then selected the Printer
and model and
Just to confirm, this problem/bug remains in Kubuntu Lucid Lynx 10.04
32-bit which I installed this morning - a fresh installation from LiveCD
burned last night. It is really a PITA not to have a functioning USB
printer.
--
xerox usb printer not recognized in Ubuntu 9.10
No need to attach the outputs - running the command results in:
p...@myotherbrain:~$ sudo /usr/lib/cups/backend/usb out 2err
Segmentation fault
However, the two files were created, but the out file is zero bytes:
p...@myotherbrain:~$ dir
total 68
drwxr-xr-x 2 paul paul 4096 2010-03-06 20:59
I reported basically, the same 'bug' on the KDE Bug Tracking System
(https://bugs.kde.org/show_bug.cgi?id=214932). My Panasonic KX-P4410
printer, connected to one of my laptops USB ports in Kubuntu Karmic
Koala 9.10 simply isn't recognized by CUPS, so I can't configure it.
This same printer, same
giorgos on 2009-11-10
Changed in cups (Ubuntu):
status:Fix Committed → Fix Released
My udev version is:
apt-cache show udev | grep Version
Version: 147~-6.1
Version: 147~-6
My USB printer does not work in Kubuntu Karmic:
Kernel 2.6.31-17-generic i686 (32 bit) Distro Ubuntu 9.10 karmic
System:Kernel 2.6.31-17-generic i686 (32 bit) Distro Ubuntu 9.10 karmic
CUPS: 1.4.1 (Installed Version: 1.4.1-5ubuntu2.1)
modinfo usblp:
filename: /lib/modules/2.6.31-17-generic/kernel/drivers/usb/class/usblp.ko
license:GPL
description:USB Printer Device Class driver
author:
Also, CUPS does not see this USB printer either.
--
usblp Kernel module needs to be removed and /dev/bus/usb/*/* made accessible
for USB printers to work with CUPS 1.4.x
https://bugs.launchpad.net/bugs/420015
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Running Kubuntu Jaunty 9.04 KDE 4.3.2. My Graphics consist of:
Graphics: Card Intel Mobile 945GM/GMS 943/940GML Express Integrated Graphics
Controller X.Org 1.6.0 Res: 1440x...@59.9hz
GLX Renderer Mesa DRI Intel 945GM GEM 20090326 2009Q1 RC2 x86/MMX/SSE2 GLX
Version 1.4 Mesa 7.4
In Kubuntu
I was going to raise this as a separate bug but might be related here. I
installed Ubuntu server 9.04 on a PIII with an old 3com network card.
Everything worked with the card recognised and using eth0 but I discovered it
was only connecting at 10 meg. I discovered this is a known issue and
Public bug reported:
Binary package hint: obm
User issue, tried to install but not sure how to configure or remove
now.
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage:
ErrorMessage: subprocess post-installation script returned error exit status 1
Package:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/28657511/Dependencies.txt
** Attachment added: VarLogDistupgrade200906190809.gz
http://launchpadlibrarian.net/28657512/VarLogDistupgrade200906190809.gz
--
package obm-storage 2.1.10-0ubuntu2 failed to install/upgrade:
Public bug reported:
Running Kubuntu 8.10 on i386 platform (Toshiba Satellite P105-S6147).
Upgraded from KDE 4.1.4 to KDE 4.2.00. Upon rebooting, and after logging
in through KDM, I get a pop-up error notification:
Error - Plasma Workspace
The process for the trash protocol died unexpectedly.
Philipp Kern wrote on 2008-06-25:
3. ACPI trouble with power off. Those people will get System halted
with kernel messages activated and can fix it by tweaking their ACPI
kernel settings
Not true here. I have a Toshiba Satellite P105-S6147 (dual-core T2060,
1024MB DDR2 SDRAM) and due to the
IT WORKS!
Okay, as a subscriber to this bug, I received the notice about migrating
the bug to the new linux package. So, I downloaded and burned the
LiveCD of Intrepid Ibex Alpha 3 (Kubuntu) today. I'm running it from the
LiveCD at the moment. I pulled out my Kingston 5GB pcmcia HD and
Reviewing https://wiki.ubuntu.com/Bugs/FindRightPackage gave me some
insight into looking for evidence of what's happening. I looked at my
.xsessions-errors file, filtered through grep on kate and found
interesting things! I moved the file and logged out and rebooted. This
ensured a new
That is interesting! Before you posted your comment, I had noticed that the
.krunnerrc file appeared to contain corruption:
Public bug reported:
Hardy Heron running KDE 4.1.00
Starting today - August 1, 2008 - logging in from KDM results in
multiple open sessions of Kate, all with an empty document. It started
with four such sessions. It's now up to six.
The only 'fix' is to remove the hidden .kde4 folder in the
May 25, 2008
Running 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux
modinfo pcmcia shows:
filename: /lib/modules/2.6.24-16-generic/kernel/drivers/pcmcia/pcmcia.ko
alias: ds
license:GPL
description:PCMCIA Driver Services
author: David Hinds
The output of /var/log/kern.log when inserted and subsequently removed
the Kingston PCMCIA 5G Hard Drive:
May 25 13:19:17 laptop kernel: [12996.907016] pccard: PCMCIA card inserted into
slot 0
May 25 13:19:17 laptop kernel: [12996.907026] cs: memory probe
0xd010-0xd01f: excluding
Please close/cancel/delete this report. Found out it was my fault. I had
compiled the ALSA driver without the necessary parameter. Recompiled the
driver and sound works and KMix is fine.
** Summary changed:
- Kmixer cannot be found
+ Kmixer cannot be found - FIXED
--
Kmixer cannot be found -
Thank you.
--- [EMAIL PROTECTED] wrote:
From: Ralph Janke [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bug 189381] Re: Kmixer cannot be found - FIXED
Date: Thu, 07 Feb 2008 00:18:13 -
Close this report as to the request of the reporter
** Changed in: ubuntu
Status: New =
Public bug reported:
Running Kubuntu Gutsy 7.10, kernel 2.6.22-14-generic #1 SMP
The following packages were identified by Adept Notifier for upgrade last night
(2008-02-04):
linux-headers-2.6.22-14
linux-headers-2.6.22-14-generic
linux-image-2.6.22-14-generic
linux-libc-dev
After these
Tested using the backup copy of the updated kernel. That did not fix the
problem. KMix still has the red X and still shows KMixer cannot be
found
--
Kmixer cannot be found
https://bugs.launchpad.net/bugs/189381
You received this bug notification because you are a member of Ubuntu
Bugs, which is
07:46:47 -
Am Donnerstag, den 31.01.2008, 03:46 + schrieb Paul L.:
Why is http://bugzilla.kernel.org/show_bug.cgi?id=9459 marked as
'closed?' The problem remains in the current Gutsy kernel. I still have
no access to my Kingston 5G PCMCIA hard drive.
This mean the patch is available
Why is http://bugzilla.kernel.org/show_bug.cgi?id=9459 marked as
'closed?' The problem remains in the current Gutsy kernel. I still have
no access to my Kingston 5G PCMCIA hard drive.
--
[pata-pcmcia] failed to set xfermode
https://bugs.launchpad.net/bugs/83471
You received this bug notification
Nope. This is the portion form my current dmesg log (in Feisty), which is just
a bit different that what Gutsy logged, but essentially the same. My Kingston
5G pcmcia HD is being recognized but not getting set up for access.
[ 26.192474] ata3: PATA max PIO0 cmd 0x00012040 ctl 0x0001204e bmdma
I confirm that moving the file system-settings-merge.menu from
/etc/xdg/menus/kde-applications-merged to /etc/xdg/menus/applications-
merged works. Please mark this bug as confirmed and note the fix that
corrects it. Please have the developers move this into production for an
update to KDE 3.5.8
I too, have this issue. I upgraded KDE yesterday from 3.5.6 to 3.5.8. K
Menu | System Settings now crashes on launch with SIGSEGV. Backtrace was
useless. I did install (afterwards) kdelibs-dbg and kdebase-dbg, but the
backtrace results still only report:
(no debugging symbols found)
Using host
As a note. With kdelibs-dbg and kdebase-dbg packages installed, running
backtrace does show four additional entries (#1, #2, etc), but you can't
capture them - the screen clears and the previously posted trace result
is all you get.
--
systemsettings crashing in KDE 3.5.8
Public bug reported:
alsamixer only shows Master PCM Caller ID and Off-Hook
Sound is heard - volume can be controlled for PCM audio ONLY
system beep sound cannot be controlled - it's Very loud
no other mixer channels can be found or controlled with alsamixer
Same problem exists with other
1 - 100 of 112 matches
Mail list logo
