Public bug reported:
The session save / restore function in KDE5 no longer respects the
virtual desktops that the applications were started in.
To duplicate:
-- Configure multiple virtual desktops (I'm using 4).
-- Start a dolphin session in Desktop 1, and a Konsole session in Desktop 4.
-- Log
Public bug reported:
Similar to Bug #1455323. Session save / restore no longer seems to work
at all with konsole.
To duplicate:
-- Start a konsole window.
-- Open multiple tabs in different directories.
-- Have the desktop session set to restore previous session on login.
-- Logout.
-- Log back
Completely reinstalled Kubuntu 13.10 from scratch, and the bug seems to
have disappeared.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1207217
Title:
Inkscape: Unable to change or select any font
Bug is still present in Ubuntu 13.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1207217
Title:
Inkscape: Unable to change or select any font
To manage notifications about this bug go to:
Just tested with the latest Inkscape ubuntu PPA
(https://launchpad.net/~inkscape.dev/+archive/trunk, 2013-08-13) and the
bug is still present.
** Also affects: inkscape
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
to a font that's available under both windows and
Ubuntu, (I used Arial)
3) Observe that the font is successfully changed under Windows, but
fails under Ubuntu.
Attached a minimal test file, and the same file exported to PDF under
Ubuntu and Windows.
On 01/08/13 16:18, Lixin Chin wrote:
Public bug
Public bug reported:
Selecting any font in inkscape fails silently. Although the new font
appears to be selected in the font drop-down list, the actual text never
changes.
To replicate:
1) Start a new document in inkscape
2) Use the Text tool and type something.
3) Select the text that was just
To everyone looking for a quick fix to this issue:
Grab the packages 'fuse' and 'libfuse2' from the debian package archive.
Get the package for your appropriate architecture (probably amd64 if
you're using 64-bit, else i386).
http://packages.debian.org/sid/libfuse2
Two months using fuse and libfuse2 2.9.2-2 from debian sid, and no
problems.
Hopefully this gets fixed officially soon. Ubuntun 13.04 looks like its
going to be using fuse 2.9.0 which has this bug as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've tried install the fuse and libfuse2 packages from debian sid
(2.9.2-2) under amd64. Using the same ntfs-3g as currently in ubuntu
12.10.
It's only been a couple of days, but so far so good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Direct link to the fuse patch from the archlinux bug report which
purports to fix this issue:
http://fuse.git.sourceforge.net/git/gitweb.cgi?p=fuse/fuse;a=commit;h=1061a0a2d90148bd2e7f32e1e694399db2dbe087
Looks like fuse 2.9.2 is packaged for debian sid
(http://packages.debian.org/sid/fuse), I
Public bug reported:
* Trying to install the cantor package gives an error message about
unmet dependencies:
sudo apt-get install cantor
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you
Public bug reported:
Upgrading from Kubuntu 12.04 to 12.10 using the muon upgrader, and
received an error message when installing both language-selector-kde and
language-selector-common (0.90 all)
subprocess new pre-removal script returned error exit status 1
Finishing with:
installArchives()
I've been seeing the same problem as #8 while trying to upgrade from
12.04 to 12.10:
dpkg: error: duplicate file trigger interest for filename `/usr/lib/gdk-
pixbuf-2.0/2.10.0/loaders' and package `libgdk-pixbuf2.0-0:amd64'
Manually removing
/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders
Testing:
-- Enabled precise-proposed repository as in
https://wiki.ubuntu.com/Testing/EnableProposed.
-- Installed hplip and dependencies from the proposed repository (log attached)
-- Verified that printer-driver-postscript-hp is now recommend by hplip.
-- Verified that printing to the M551
Attached
On 25/06/12 17:21, Till Kamppeter wrote:
Can you run the commands
dpkg -l | grep hplip
dpkg -l | grep printer-driver
dpkg -l | grep -i postscript
lpinfo -m | grep -i laserjet | grep 500
and post the output here? Thanks.
** Attachment added: grep_hplip.txt
Installing the 'printer-driver-postscript-hp' package has solved my
problem.
It could be because my system has been upgraded continuously without a
fresh install since 10.04, but the 'printer-driver-postscript-hp'
doesn't seem to be installed by default.
A brief search using synaptic, and it
Thank you very much for your help, initial tests with the driver from
the 'printer-driver-postscript-hp' package went well, and everything
seems to be working perfectly now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached the output files requested. There are several printers on the
work network, so I've edited out the lines directly related the the M551.
As far as I can tell looking through the CUPS driver selection dialog
using the web interface http://localhost:631, and use the KDE printer
The printer appears to work perfectly if assigned the Generic PCL 6/PCL
XL Printer foomatic/pxlcolor ppd
(/usr/share/ppd/ghostscript/model/pxlcolor.ppd).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The HP LaserJet Enterprise 500 Color m551dn printer is claimed to be
fully supported using HPLIP 3.11.10 (http://hplipopensource.com/hplip-
web/models/color_laserjet/hp_laserjet_500_color_m551.html), so it should
be supported under the 3.12.2 version shipped with Ubuntu
dmesg.log *without* blacklisting uas (only dmesg and lspci outputs
differ in this case)
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/828471/+attachment/2938032/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
lspci-vvnn.log *without* blacklisting uas (only dmesg and lspci outputs
differ in this case)
** Attachment added: lspci-vvnn.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/828471/+attachment/2938033/+files/lspci-vvnn.log
--
You received this bug notification because you are a
** Attachment added: dmesg.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/828471/+attachment/2938000/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/828471
Title:
** Attachment added: lsusb.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/828471/+attachment/2937997/+files/lsusb.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/828471
Title:
Attached files *with* uas blacklisted:
** Attachment added: uname-a.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/828471/+attachment/2937995/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: proc_version_signature.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/828471/+attachment/2937998/+files/proc_version_signature.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: uname-a.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/828471/+attachment/2937999/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/828471
Title:
Attached files *with* uas blacklisted:
** Attachment added: lspci-vvnn.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/828471/+attachment/2937996/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tested using the v3.3-rc7-precise kernel image from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc7-precise/
And it works!
The uas module is unblacklisted:
etc/modprobe.d% grep -r uas *
blacklist-usb.conf:# blacklist uas
But it doesn't load anyway:
lsmod | grep uas
[1]2704 done
And with the 2012-03-25 mainline kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/
It likewise works, and doesn't load the uas module:
lsmod | grep -i uas
[1]2717 done lsmod |
2718 exit 1 grep --color=auto -i uas
Once again, no
I can confirm that adding the line blacklist uas into
/etc/modprobe.d/blacklist.conf (or /etc/modprobe.d/blacklist-usb.conf in
my case) solves the bug.
The harddrive seems to work perfectly over USB3.0 once this is done,
even without adding a FAT32 partition.
Oddly in kubuntu, plugging in the
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/828471 looks to be
the same bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875523
Title:
LaCie usb storage doesn't mount
To manage
Tested in oneiric 11.10 with linux-image-3.0.0-13-generic and the bug is
still present.
** Attachment added: dmesg_3.0.0-13-generic.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/828471/+attachment/2604631/+files/dmesg_3.0.0-13-generic.txt
--
You received this bug notification
sudo fdisk -l; echo; sudo parted -l;
--
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512
Tested in oneiric 11.10, and the bug is still present.
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/828471/+attachment/2569208/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Another search of the ubuntu forums turned up this user who seems to have the
identical problem with the same model of HDD:
http://ubuntuforums.org/showthread.php?t=1815922
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirming that the bug still exists in the latest Ubuntu kernel,
2.6.38-11-generic (64-bit).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/828471
Title:
USB3.0 External Harddrive fails to detect
Public bug reported:
Ubuntu 11.04, kernel version 2.6.38-10-generic. 64-bit arch.
Drive is a Lacie 1TB USB3.0 / Firewire 800 2.5 external harddrive:
http://www.lacie.com/au/products/product.htm?id=10553
Plugging the drive into the usb3 port just results in xhci_hcd errors,
and the drive is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/828471
Title:
USB3.0 External Harddrive fails to detect
To manage notifications about this bug go to:
Attaching dmesg output.
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux-lts-backport-natty/+bug/828471/+attachment/2287659/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oops, previous dmesg missed a few lines from the scsi driver which are
output a few seconds after the xhci_hcd failures.
** Attachment added: dmesg.txt
https://bugs.launchpad.net/ubuntu/+source/linux-lts-backport-natty/+bug/828471/+attachment/2287660/+files/dmesg.txt
--
You received this
Attached the dmesg output when plugging the same drive into a usb2.0
port on the same computer.
Although it says its attached the disk to sdb,
sudo fdisk -l /dev/sdb
just returns with no output.
** Attachment added: dmesg_usb2.txt
It appears to be related to this:
https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=717633
error in Fedora 15, and to this:
http://ubuntuforums.org/showthread.php?p=11142776
posting on the ubuntu forums.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm getting the same problem, laptop-mode-tools fails to install using
Kubuntu 11.04 on x64_64 with the same error message as #1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779435
Title:
@IKT:
Oops! My bad, I was in a hurry and had assumed that the -8 version number
corresponded to the .3 patch number on the mainline kernel.
Installed the mainline kernel and things seem to be working so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I can confirm this bug (or one very like it) is *not* fixed.
Arch is x86_64,
Device is an ASUS EEE-PC 1005PE
lspci:
02:00.0 Network controller: Atheros Communications Inc. AR2427 Wireless Network
Adapter (PCI-Express) (rev 01)
uname -a:
Linux hostname 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11
Public bug reported:
As per the summary. Oddly enough, I'm sure it was working (although
upside down, but that's a different matter) just a few weeks ago.
lsusb:
Bus 001 Device 013: ID 13d3:5122 IMC Networks
$ luvcview
luvcview 0.2.6
SDL information:
Video driver: x11
A window manager is
** Attachment added: dmesg.log
https://bugs.launchpad.net/bugs/739133/+attachment/1925602/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/739133
Title:
Asus inbuilt webcam
** Attachment added: dmidecode.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/739133/+attachment/1925603/+files/dmidecode.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/739133
Title:
** Attachment added: lspci-vnvn.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/739133/+attachment/1925604/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/739133
** Attachment added: uname-a.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/739133/+attachment/1925606/+files/uname-a.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/739133
Title:
** Attachment added: version.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/739133/+attachment/1925612/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/739133
Title:
I'm seeing the same problem, with plasma-widget-networkmanagement. An
identical issue seems to be affecting network-manager-kde
(knetworkmanager).
But it works perfectly when using the gnome network manager (network-
manager-gnome).
My network isn't using a CA Cert, could that be causing a
I can confirm that applying Andrew Punnett's patch to /var/lib/dpkg/info
/texmacs-common.postinst fixes the problem.
Kubuntu Lucid 10.04, texmacs-common 1.0.7.3-3.
--
package texmacs-common 1:1.0.7.2-1 failed to install/upgrade: subprocess
installed post-installation script returned error exit
Same problem here with an ASUS N61Ja and ATI Mobility Radeon HD5730.
Kubuntu 10.04 using KDE / KWIN.
--
[Multi-GPU] No virtual terminals on radeon HD 3200/3400
https://bugs.launchpad.net/bugs/540547
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I've run into this bug as well (kopete 4.4.2-0ubuntu4, Kubuntu 10.04,
amd64) although I have no idea what I did to trigger it.
The previous work around doesn't work for me -- there doesn't seem to be
a reset color font button anywhere. font. There don't appear to be
any toolbar buttons for
I've discovered another work around:
Quite Kopete, then open up ~/.kde/share/config/kopeterc and delete all
the settings under the [chatwindow_{blahblahblah}] sections,
especially the bits about TextBgColor, then restart kopete, and all the
chat windows will be back to normal.
--
Invisible text
According to upstream: https://svn.boost.org/trac/boost/ticket/3371
its more general than that, everything that uses boost::mpl up to version 1.40
will fail to compile with g++ 4.4
** Bug watch added: Boost Trac #3371
http://svn.boost.org/trac/boost/ticket/3371
--
boost gil library examples
Public bug reported:
Upstream ticket: https://svn.boost.org/trac/boost/ticket/3371
This seems to be a problem with boost::mpl and everything using it
(including boost::gil). Any use of boost::mpl results in a compile
failure with g++4.4, which is the default version of g++ for Lucid.
Manually
Tried the same thing with boost 1.40, and the same problem occurs there
as well.
(can't figure out how to have launchpad link this bug report to
boost1.40).
--
boost gil library examples fail to compile
https://bugs.launchpad.net/bugs/566541
You received this bug notification because you are a
Retested with g++-4.3 and it seems to work, the example compile
successfully.
This may be related to
https://bugs.launchpad.net/ubuntu/+source/boost/+bug/436470 although
that bug was just for boost 1.38 and I'm seeing the same problems with
boost 1.40.
--
boost gil library examples fail to
Public bug reported:
The GIL sub-library of LibBoost comes with several examples. I'm trying
to compile the dynamic_image.cpp example in a working directory using:
g++ dynamic_image.cpp
However it fails, as does any attempt to compile any code using the GIL
library to attempt to read images
** Attachment added: g++ attempt to compile libboost gil example.
http://launchpadlibrarian.net/44807210/boost_dump.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/44802907/Dependencies.txt
--
boost gil library examples fail to compile
** Attachment added: hibernate.sh
http://librarian.launchpad.net/7489484/hibernate.sh
--
Standard hibernate not running
https://bugs.launchpad.net/bugs/57
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
/etc/acpi/hibernate.sh should be the standard installed from the acpi-
support package. The only line I changed is line 31, since I prefer to
use disk labels instead of uuids. It seemed to work quite well in edgy.
Here's my copy of /etc/initramfs-tools/conf.d/resume as well.
** Attachment added:
Public bug reported:
Binary package hint: powermanagement-interface
Kubuntu 7.04, Samsung X50 laptop.
Choosing Hibernate from the logout menu does nothing, it only locks the
screen and never even tries to write the image to disk.
Running 'sudo /usr/sbin/pmi action hibernate force' directly
Public bug reported:
Binary package hint: acpi-support
Kubuntu feisty 7.04, Samsung X50 laptop.
As the summary indicates, I can hibernate my laptop using uswsusp
directly by typing 'sudo s2disk' at a console. It suspends and resumes
with no problems.
I then edited
Public bug reported:
Binary package hint: lilypond
The lilypond-data package PreDepends on tetex-bin. It would be better if
it allowed texlive to be used in place of tetex.
I believe this is the case with the current Debian unstable version of
the package:
Public bug reported:
Binary package hint: kde-guidance-powermanager
See the summary.
Both klaptopdaemon and the gnome cpu frequency applet allow the user to
choose the specific kernel-space governor used to scale cpu frequency
(ondemand, powersave, performance, conservative or userspace). It
Public bug reported:
Binary package hint: kubuntu-artwork-usplash
The kubuntu usplash progress bar doesn't display correctly at 800x600
resolution, although it works fine at 1024x768. The standard ubuntu
usplash screen works at both resolutions.
I set the resolution by adding vga=788 to the
71 matches
Mail list logo
