Public bug reported:
After locking the screen or suspending my computer, I cannot re-login.
Though my password is correct (there ist no verification problem shown),
the login screen does not disappear, but requests my password again.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg
*** This bug is a duplicate of bug 805087 ***
https://bugs.launchpad.net/bugs/805087
I get this issue constantly with all updates applied as of today:
(1) Start a new desktop session
(2) Open a full-screen Thunderbird on workspace 4
After doing those steps there is about 50% that Unity
I can confirm that this bug is NOT fixed.
I get this issue constantly with all updates applied as of today:
(1) Start a new desktop session
(2) Open a full-screen Thunderbird on workspace 4
After doing those steps there is about 50% that Unity renders it's windows
below all other windows.
Also,
For me the issue vanished with linux-image-2.6.31-4-generic
(2.6.31-4.22).
During boot there are still these warnings:
Jul 25 12:29:16 vrock kernel: [9.259545] device-mapper: table: 252:6: sda
too small for target
Jul 25 12:29:16 vrock kernel: [9.259547] device-mapper: table: 252:6: sdb
The same happens here with an Intel ICH8 Raid. Ubuntu itself is not
installed on any of the raid drivers (sda and sdb), but raid partitions
get mounted later.
This problem is not present in the kernel of Karmic alpha2 (2.6.30), but
appeared after the update of the current Karmic kernel 2.6.31-3.
Update: Still present in current Jaunty.
--
Setting the number of workspaces under compiz does not also set the keybindings
https://bugs.launchpad.net/bugs/150918
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
*** This bug is a duplicate of bug 150918 ***
https://bugs.launchpad.net/bugs/150918
Thanks, I did not find that bug when I did my search.
Regarding the gconf component, it's the right one. Changing them has
effect under compiz too.
--
Missing Shortcuts for switching to workspace n, n2
Public bug reported:
Binary package hint: gnome-control-center
There are only keyboard shortcuts for
* switch to workspace 1
* switch to workspace 2
I have 4 workspaces and thus cannot assign keyboard bindings for the
other 2 workspaces.
Distribution:
Ubuntu jaunty (development branch)
I should mention that the configs are there and accessible through gconf-editor:
The key names are /apps/metacity/global_keybindings/switch_to_workspace_n for 0
n 13.
gnome-keybinding-properties seems just to be hardcoded to show only
bindings for 2 workspaces, which is the default on Ubuntu.
I got the very same crash and backtrace when trying to install a current
svn snapshot of kdesupport/qca. This is on amd64.
** Changed in: cmake (Ubuntu)
Status: New = Confirmed
--
cmake crashed with SIGSEGV in cmELF::GetRPath()
https://bugs.launchpad.net/bugs/244782
You received this bug
Forgot to mention: The error is _not_ there when I unlock the root
account with 'sudo passwd root'. chfn fails only when root is locked via
'passwd -l root'.
--
'Account has expired' message when adding a new user
https://bugs.launchpad.net/bugs/238755
You received this bug notification because
Changing the package from 'adduser' to 'shadow' as the actual command
which fails is /usr/bin/chfn which originates from the shadow source
package.
** Changed in: shadow (Ubuntu)
Sourcepackagename: adduser = shadow
--
'Account has expired' message when adding a new user
I have the same error, when trying to use chfn. This also has the neat
effect, that it breaks installation of mysql-server, as the pre-install
script fails.
This is the command, which fails during the mysql-server pre-installation
script:
$ sudo /usr/bin/chfn -f 'MySQL Server' mysql
Your account
Yes, this is an configuration issue. By default Ubuntu's root account is
disabled and chfn should surely handle this configuration and just work.
But it does not.
https://help.ubuntu.com/community/RootSudo tells to execute 'passwd -l
root' to re-disable the root account. As I understand it this
Setting the package to dmraid, as this is probably a bug in dmraid's
initrd magic.
** Changed in: dmraid (Ubuntu)
Sourcepackagename: None = dmraid
--
initramfs prompts because of dmraid
https://bugs.launchpad.net/bugs/247027
You received this bug notification because you are a member of Ubuntu
The same here. The dmraid devices (in my case
/dev/mapper/isw_bgjcdcfheh_volume*) are not there when the boot scripts try to
mount rootfs.
Only /mapper/control is there.
dmraid -ay at the busybox prompt creates all dmraid devices under
/dev/mapper/ (and triggers udev to create my LVM volume
Maybe an other solution could be the usage of update-alternatives
instead of dpkg-divert. But that requires that all OpenGL providing
packages cooperate and probably has other problems too, of which I may
not be aware of.
Maybe someone will come up with an better idea, but for the meantime:
The problem is that the nvidia-glx-177 package is missing a diversion on
/usr/lib32/libGL.so.1 like it has for /usr/lib/libGL.so.1.
** Changed in: nvidia-graphics-drivers-177 (Ubuntu)
Sourcepackagename: ia32-libs = nvidia-graphics-drivers-177
Status: New = Confirmed
--
Intrepid: ia32-lib
Looks like the new version (1.5.4-dfsg-1) is out:
http://packages.debian.org/sid/virtualbox-ose
This new version should also be able to build against kernel 2.6.24
which is needed for Hardy.
BTW, shouldn't the status be 'in progress' if someone is already working
on a merge?
Also I think
Yes, the problem is Hardy's current version of virtualbox-ose is not compatible
with the new default kernel (2.6.24).
Hardy's virtualbox-ose package needs an upgrade to version 1.5.4 to be able to
build against hardy's kernel.
This is already being worked on, see bug #156210 .
** Changed in:
Public bug reported:
Binary package hint: fontconfig-config
SUMMARY:
fontconfig-config's default configuration is broken.
This is in Hardy, fontconfig-config version 2.5.0-2ubuntu2.
DETAIL:
fontconfig-config installs configuration files under /etc/fonts/conf.d.
But all config files should be
*** This bug is a duplicate of bug 178234 ***
https://bugs.launchpad.net/bugs/178234
Thank you for reporting, but this issue is already filed as bug #178234 GTK
themes doesn't work.
I'll thus mark it as duplicate.
** This bug has been marked a duplicate of bug 178234
GTK themes doesn't
Changing the status to confirm' because several people can reproduce
this issue
** Changed in: kubuntu-meta (Ubuntu)
Status: New = Confirmed
--
GTK themes doesn't work.
https://bugs.launchpad.net/bugs/178234
You received this bug notification because you are a member of Ubuntu
Bugs,
Yes, GTK+ themes seem to not apply under KDE currently. We only get the rather
ugly default unthemed GTK+ look.
GTK+ Themes work fine under Gnome through.
--
GTK themes doesn't work.
https://bugs.launchpad.net/bugs/178234
You received this bug notification because you are a member of Ubuntu
I would be a good idea to rebuild all packages depending on libungif4
for universe too. Otherwise users will not be able to install various
packages because libungif4 and libgif4 cannot be installed side by side.
--
transition to libgif
https://bugs.launchpad.net/bugs/174252
You received this
Could this be related to the fact that fontconfig-config installs files
in /etc/fonts/conf.d/ which should be in /etc/fonts/conf.avail/ instead
(i.e. all the non-symlink files)?
--
[hardy] fonts smaller after update
https://bugs.launchpad.net/bugs/174229
You received this bug notification
Yes, many paths in /etc/apparmor.d/abstractions/kde are wrong for
Ubuntu/Kubuntu.
Here is a kde file, in which I have corrected the paths. I am sure that
it's far from complete (and may contain an error or two) but it's a
start.
** Attachment added: kde apparmor abstraction
I am not able to reproduce this issue in Gutsy.
--
xserver-xorg config script hangs (1:7.1.1ubuntu3)
https://bugs.launchpad.net/bugs/66415
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
The new version was uploaded, see bug #131975.
** Changed in: kde-style-qtcurve (Ubuntu)
Status: Confirmed = Fix Released
--
kde-style-qtcurve makes amarok menus appear as blank grey panels (Ubuntu)
https://bugs.launchpad.net/bugs/126577
You received this bug notification because you
Public bug reported:
Binary package hint: kde-style-qtcurve
These are 3 Packages (I didn't filed separate bug reports because it would be
bad to only sync part of these widget style packages, I hope that's okay):
- kde-style-qtcurve
- gtk2-engines-qtcurve
- qtcurve
Versions in Gutsy:
-
I can confirm this and filed a request to sync the 0.52.3-1 version from Debian
Unstable,
see Bug #131975 .
** Changed in: kde-style-qtcurve (Ubuntu)
Status: New = Confirmed
--
kde-style-qtcurve makes amarok menus appear as blank grey panels (Ubuntu)
The same here with versions
spamassassin 3.2.2-0ubuntu1
razor 2.810-2
** Changed in: spamassassin (Ubuntu)
Status: New = Confirmed
** Bug watch added: Debian Bug tracker #403955
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=403955
** Also affects: spamassassin (Debian) via
At least the sky2-tx-kick.patch applies fine to the 2.6.20 kernel. But I
can't test it, because currently I don't have access to a sky2 network
controller.
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://bugs.launchpad.net/bugs/83009
You received this bug notification
Okay, as this seems to be fixed in Gutsy, I'll close the bug report.
If anyone still can reproduce it, please feel free to reopen this bug report.
Thanks.
** Changed in: emacs-snapshot (Ubuntu)
Status: Incomplete = Fix Released
--
emacs-snapshot-gtk display
Yes, I am not able to reproduce this with current Gutsy.
--
emacs-snapshot-gtk display
https://bugs.launchpad.net/bugs/67422
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.ubuntu.com
Yes, this is filed as bug in amarok at
http://bugs.kde.org/show_bug.cgi?id=98519 which itself is a duplicate of
http://bugs.kde.org/show_bug.cgi?id=106115 .
I think a nice thumbnail view to select the cover from the ones which
are available would be a much more user friendly interface then just
The same case was reported upstream at
http://bugs.kde.org/show_bug.cgi?id=142140 .
I quote from there: That file is not a pdf file, PDF files must end with %%EOF
and this one ends with %%EO, once corrected the file works correctly.
So I would say, your bank has a bug in the code which
I'll mark this as invalid.
It's right that the log files mentioned in Dave's bug report are not
rotated by logrotate.
The reason is that sysklogd already comes with cron jobs to rotate these
files itself. So logrotate is not needed to rotate these files too. If
logrotate would include these logs
Does devscripts really need a hard dependency on fakeroot?
debuild can also be used as root (not uncommon to do under a chroot
environment), or via the --rootcmd option with super or sudo.
Currently devscripts recommends fakeroot. Isn't this better than a hard
dependency given that debuild can
Actually this is expected behaviour on Linux.
You cannot have a file and a directory with the same name (on file
system level, both, normal files and directories are 'files' and two in
a directory can not have the same name), just as you cannot have two
directories or two text files with the same
Yes, this is a known bug in KDE's pager.
I added a link to the upstream bug. There were some fixes to kpager in
the latest KDE version to work better with beryl/compiz but evidently
there are still issues.
** Changed in: kdebase (Ubuntu)
Sourcepackagename: beryl-core = kdebase
** Bug watch
This looks like KDE bug 146638:
http://bugs.kde.org/show_bug.cgi?id=146638
Which version of Kopete are you using?
** Also affects: kdenetwork (upstream) via
http://bugs.kde.org/show_bug.cgi?id=146638
Importance: Unknown
Status: Unknown
--
Gmail password problem
Thanks, I added your information to the upstream bug report.
** Changed in: kdenetwork (Ubuntu)
Status: New = Confirmed
--
Gmail password problem
https://bugs.launchpad.net/bugs/121001
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for
Creating a new dir under the console works only if there is no file with
the same name:
# cd /tmp
# ls settings
ls: settings: No such file or directory
# touch settings
# ls settings
settings
# mkdir settings
mkdir: cannot create directory `settings': File exists
--
[kubuntu] konqueror: cannot
No problem. I'll close it again. :-)
** Changed in: kdebase (Ubuntu)
Status: New = Invalid
--
[kubuntu] konqueror: cannot create a folder if a file of the same name already
exists
https://bugs.launchpad.net/bugs/120350
You received this bug notification because you are a member of
** Bug watch added: Debian Bug tracker #429827
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429827
** Also affects: qtstalker (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429827
Importance: Unknown
Status: Unknown
--
Image properties shows displayed width
** Changed in: Debian
Sourcepackagename: qtstalker = None
Importance: Unknown = Undecided
Bugwatch: Debian Bug tracker #429827 = None
Status: Unknown = Unconfirmed
** Changed in: Debian
Status: Unconfirmed = Rejected
--
Image properties shows displayed width and height,
** Bug watch added: Debian Bug tracker #429827
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429827
** Also affects: qtstalker (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=429827
Importance: Unknown
Status: Unknown
** Changed in: qtstalker (Ubuntu)
Public bug reported:
A new upstream version was released.
kde3-style-qtcurve and gtk2-engines-qtcurve are already at version 0.51
in Gutsy.
kde4-style-qtcurve should be updated too.
The new upstream version also contains a 'fix' to some wrong license text, i.e.
misleadingly some files included
Here is a debdiff from kde4-style-qtcurve_0.50-0ubuntu1 to kde4-style-
qtcurve_0.51-0ubuntu1:
Changelog:
* New upstream version
* Updated debian/copyright to reflect upstream's license clarification,
everything is GPL-2, the MIT license text in some files was a mistake
** Attachment
Oops, I forgot the following change in debian/copyright:
- Copyright (C) 2007 by Craig Drummond [EMAIL PROTECTED]
+ Copyright (C) 2003-2007 by Craig Drummond [EMAIL PROTECTED]
(the kde4 port of qtcurve started 2007 but contains some older code which is
copyright
2003-2007 by Craig Drummond)
kde4-style-qtcurve (0.51-0ubuntu1) gutsy; urgency=low
* New upstream version(LP: #120394)
* Updated debian/copyright to reflect upstream's license clarification,
everything is GPL-2, the MIT license text in some files was a mistake
-- Andreas Simon [EMAIL PROTECTED] Thu, 14
I think libqt0-ruby1.8-qt4 (1.4.6-0ubuntu1) is now obsoleted by libqt4-ruby1.8
(1.4.7-4).
libqt4-ruby1.8 is not affected from this bug and also follows the
Debian-Maintainer-Field Spec.
But is this really the case? If yes than libqt4-ruby1.8 should probably have
'replaces' set against
*** This bug is a duplicate of bug 117119 ***
https://bugs.launchpad.net/bugs/117119
Thanks for taking the time to report this bug and helping to make Ubuntu
better. This particular bug has already been reported and is a duplicate
of bug #117119 and is being marked as such. Please feel free
Public bug reported:
libpoppler-qt-dev 0.5.4-4ubuntu1 in current Gutsy is missing a header file:
poppler-link-qt3.h
poppler-qt.h includes poppler-link-qt3.h but the package doesn't install
poppler-link-qt3.h.
So all packages which use poppler-qt.h fail to compile.
** Affects: poppler (Ubuntu)
Added a debdiff for the trivial fix.
** Attachment added: Debdiff to install the missing header
http://librarian.launchpad.net/7859186/poppler-debdiff.diff
--
missing header file in libpoppler-qt-dev
https://bugs.launchpad.net/bugs/117388
You received this bug notification because you are a
I just saw that there is a blueprint for this at
https://blueprints.launchpad.net/ubuntu/+spec/fakeraid-support
--
dmraid / FakeRAID support should work automatically in installers.
https://bugs.launchpad.net/bugs/90235
You received this bug notification because you are a member of Ubuntu
Bugs,
I have exactly the same issue on a dual-boot system where I also use the
Ext2IFS 1.10c drivers under Windows.
BTW, the same issue happens with Knoppix 5.1.1.
--
[Feisty] Kernel crashes in ext3 dx_probe
https://bugs.launchpad.net/bugs/109177
You received this bug notification because you are a
Yes, the new udev and dmraid packages fixed it here too. Thus I'll close
the bug report.
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed = Fix Released
--
boot hangs polling for the root fs when using lvm on dmraid
https://bugs.launchpad.net/bugs/78939
You received this bug
Tim, thank you for your work. Sadly, like Darren, I too encountered
soft-lockups with that sky2.ko.2.6.20-14 (as with a complete vanilla
2.6.21-rc6 kernel). It's slightly better with this version. Removing the
module and reloading it again makes the network work again. With earlier
versions of the
I just set up a machine where rootfs is also on a lvm on top of dmraid
(an Intel ich8r board here) and get the same error.
It looks that when the init script tries to mount the rootfs the /dev/mapper/
devices are not there yet.
When doing a 'dmraid -ay' by hand it takes around 1-2 seconds till
In the meantime I encountered several soft lockups with linux image
2.6.20-14.22 too. It seems this bug is not fixed with tha latest sky2
upstream changes.
Currently I test the Yukon driver (sk98lin) from Marvell, which can be
downloaded from
Lauri, it could also be that your problem is a different one. At least
some lockups seems to be highly related to sky2 and network traffic.
Anyway, since the 3 days I run linux-image-2.6.20-13-generic version
2.6.20-13.21 I haven't encountered any new lockups. Maybe the problem is
already fixed
** Summary changed:
- BUG: soft lockup detected on CPU#0!
+ sky2 transmit timeout and soft lockup detected on CPU#0!
--
sky2 transmit timeout and soft lockup detected on CPU#0!
https://launchpad.net/bugs/83009
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The problem still persists on current Feisty with linux-image 2.6.20-12,
udev 103-0ubuntu13, and lvm2 2.02.06-2ubuntu8.
--
Root fs on LVM fails to boot
https://launchpad.net/bugs/87745
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I just saw that in /etc/udev/rules.d/70-lvm.rules the device is tested
against ENV{ID_FS_TYPE}==lvm*|LVM* to trigger the vgchange/vgscan.
But
$ grep ID_FS_TYPE /var/log/udev
ID_FS_TYPE=ext3
ID_FS_TYPE=vfat
ID_FS_TYPE=swap
ID_FS_TYPE=ntfs
ID_FS_TYPE=ext3
ID_FS_TYPE=ext3
ID_FS_TYPE=reiserfs
It adds support for a couple of cards which are not supported by
Feisty's current version:
Here is the changelog:
* Added support for Quadro FX 4600 and Quadro FX 5600.
* Added support for SLI with GeForce 8800, Quadro FX 4600,
and Quadro FX 5600.
2006-12-21 version 1.0-9746
*
*** This bug is a duplicate of bug 83009 ***
** This bug has been marked a duplicate of bug 83009
BUG: soft lockup detected on CPU#0!
--
sky2 driver hangs / softlockup
https://launchpad.net/bugs/87320
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This seems to be a bug in the sky2 network driver.
I have the same on a Gigabyte P695-DS4 rev3.3 motherboard with a Marvel
8056 chip. The higher the network traffic, the higher the probability
for the crash.
** Bug watch added: Linux Kernel Bug Tracker #7546
I remove the needs info status because the last request was answered.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Needs Info = Confirmed
--
BUG: soft lockup detected on CPU#0!
https://launchpad.net/bugs/83009
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
*** This bug is a duplicate of bug 84964 ***
JFYI, I can reproduce this bug with all kernels since 2.6.20-8,
including the latest version 2.6.20-12.20.
--
Kernel 2.6.20-8 cannot mount SATA root on ASUS P5B VM
https://launchpad.net/bugs/86156
--
ubuntu-bugs mailing list
Bug #86156 has the calltrace of modprobe's crash on a board with the
JMicron controller chip. I have the exact same calltrace on an other
board with the same JMicron chip.
I think that is the same bug as here, but only calltraces from other
people's crashes can tell for sure.
--
modprobe
Found the bug, and it's strictly related to jmicron. [...]
This is fixed in my git. It's unfortunate that I didn't get it done in
time for beta, but I will be uploading this kernel on Saturday, so by
early next week you should start seeing it on mirrors.
Great news, your effort is much
Here an other negative. Kernel 2.6.20-12.19 didn't change anything,
modprobe still crashes.
--
modprobe abnormal exit - Kernel 2.6.20-8/9/10/11/12 does not boot
https://launchpad.net/bugs/84964
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: bzr (Ubuntu Feisty)
Status: Unconfirmed = Confirmed
--
index.html contains mainly broken links
https://launchpad.net/bugs/92432
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I can confirm that these fortunes are in fortunes-min.
They probably should belong to fortunes-off
** Bug watch added: Debian Bug tracker #411907
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411907
** Also affects: fortune-mod (Debian) via
Cestulia's workaround from comment #59 worked here too (Gigabyte 965P-
DS4 mainboard with two hard discs on the jmicron controller). Everything
seems fine so far, only the old hard drives changed from beeing /dev/hd*
to /dev/sd*.
--
modprobe abnormal exit - Kernel 2.6.20-8/9/10 does not boot
Yes, this is a problem with eog which doesn't scale vector graphics
right.
** Changed in: eog (Ubuntu)
Status: Unconfirmed = Confirmed
** Bug watch added: GNOME Bug Tracker #108435
http://bugzilla.gnome.org/show_bug.cgi?id=108435
** Also affects: eog (upstream) via
*** This bug is a duplicate of bug 89378 ***
Thanks for your bug report. This particular bug has already been
reported and is a duplicate of bug 89378 and is being marked as such.
Please feel free to report any other bugs you may find.
** This bug has been marked a duplicate of bug 89378
*** This bug is a duplicate of bug 89378 ***
This crash looks like the one in bug 89378. I'll thus mark it as
duplicate. Thanks for reporting.
** This bug has been marked a duplicate of bug 89378
[apport] gnome-theme-manager crashed with SIGSEGV in strcmp()
--
Gnome theme selector crash
I mark this as 'confirmed' because there are already 2 duplicates.
** Changed in: gtk-qt-engine (Ubuntu)
Status: Unconfirmed = Confirmed
--
[apport] gnome-theme-manager crashed with SIGSEGV in strcmp()
https://launchpad.net/bugs/89378
--
ubuntu-bugs mailing list
Here is my output from 'dmesg'.
** Attachment added: dmesg output
http://librarian.launchpad.net/6804710/dmesg.txt
--
modprobe abnormal exit - Kernel 2.6.20-8/9/10 does not boot
https://launchpad.net/bugs/84964
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
And here the output of 'lspci -vvn'
** Attachment added: Output of lspci
http://librarian.launchpad.net/6804727/lspci-vvn.txt
--
modprobe abnormal exit - Kernel 2.6.20-8/9/10 does not boot
https://launchpad.net/bugs/84964
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thank you for this bug report. The issue is already fixed in the new gthumb
version in Feisty.
See also http://bugzilla.gnome.org/show_bug.cgi?id=343867
Thus I'm closing this bug because it's already been fixed in Feisty.
If you need a fix for the bug in 6.06, please follow the instructions
for
I think in the default configuration sysklogd will rotate the mentioned
logfiles itself, not logrotate. This is because logrotate is no longer
part of the default installation.
The sysklogd package comes with the cron jobs /etc/cron.daily/sysklogd
and /etc/cron.weekly/sysklogd. These rotate
I think you first need to log-out of KDE before these file options
disappear. Are they still there after you logged out and in again?
--
Uninstalling amarok doesn´t remove open with links
https://launchpad.net/bugs/52562
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
*** This bug is a duplicate of bug 72117 ***
Thanks for your bug report. This particular bug has already been
reported and is a duplicate of bug 72117 and is being marked as such.
Please feel free to report any other bugs you may find.
** This bug has been marked a duplicate of bug 72117
Here is a debdiff which fixes the issue here.
In src/backend/back_linux.c I changed the line
if(sscanf(buffer,%s %d %d,name, size, used) != 3) continue;
to
if(sscanf(buffer,%19s %d %d,name, size, used) != 3) continue;
to prevend a overflow of name[].
I attached a debdiff and will also notify
** Tags added: patch
--
Stack Smashing Prevents Use
https://launchpad.net/bugs/72117
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Can this not also be restriced by changing the permissions of
/dev/nvidia* ?
I think there is not much security gained if nclock can be run only by
root but the device to speak directly to the nvidia hardware has still
write-permission for all users.
** Changed in: nvclock (Ubuntu)
Patrice, you are right. Nautilus works because it accesses my DVD-writer
through /dev/scd0. But if I start it as a user who is in group cdrom but
not in group floppy it fails too. The default user is member of both
groups, so it doesn't have any impact that scd0's group is floppy
instead of cdrom.
I have the very same modprobe crash but with a Gigabyte 965P DS4
mainboard, which has the same Intel 965 chipset as your Asus mainboard.
I don't have any SATA hard discs connected, the only SATA device here is
a SATA DVD burner. My harddiscs are IDE drives which are connected to
the motherboards
Forgot to mention:
If I boot with break=mount the crash happens and there are no /dev/hd*
devices nor any other harddisc devices under /dev. It looks like some chipset
driver crashes or something like that, so no devices (IDE or SATA) are detected
or accessible.
--
Kernel 2.6.20-8 cannot
I just want to add that this problem is still there with feisty's
current udev version 103-0ubuntu13.
--
Wrong group for IDE cdrom/cdwriter/dvd devices
https://launchpad.net/bugs/75753
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: lvm2
Having the root filesystem on LVM fails to boot on current feisty.
I am not sure this is a duplicate of either #85617 or #83832. 85617
could be a bootloader misconfiguration and 83832 involves LVM on RAID.
What happens:
During boot, the system
Public bug reported:
Binary package hint: evolution
evolution-alarm-notify gets automatically started in KDE sessions.
This is usually unwished for because KDE comes with it's own alarm
notification system.
Proposed fix:
Add a
OnlyShowIn=GNOME;
line in
** Bug watch added: KDE Bug Tracking System #128206
http://bugs.kde.org/show_bug.cgi?id=128206
** Also affects: adeptmgr (upstream) via
http://bugs.kde.org/show_bug.cgi?id=128206
Importance: Unknown
Status: Unknown
--
adept should show download speed and ETA
** Changed in: koffice (Ubuntu)
Status: Unconfirmed = Confirmed
** Bug watch added: KDE Bug Tracking System #138337
http://bugs.kde.org/show_bug.cgi?id=138337
** Also affects: koffice (upstream) via
http://bugs.kde.org/show_bug.cgi?id=138337
Importance: Unknown
Status:
** Bug watch added: KDE Bug Tracking System #137253
http://bugs.kde.org/show_bug.cgi?id=137253
** Also affects: kdenetwork (upstream) via
http://bugs.kde.org/show_bug.cgi?id=137253
Importance: Unknown
Status: Unknown
--
Kopete overloads system
https://launchpad.net/bugs/82799
On my configuration the wronly selected font leads to colour bleeding
which makes the rendering very ugly.
This is the changelog entry from Debian's libqt3 version 3.3.7-2.
* debian/patches/61_fcfontmatch_fontwidth_fix.dpatch
Fix font matching with fontconfig. This resolves inconsistency
1 - 100 of 265 matches
Mail list logo
