Public bug reported:
It was installed from an earlier Ubuntu release, probably just doesn't
like the update.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: samba4 4.0.0~alpha18.dfsg1-4ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae
Public bug reported:
I've purchased Wacom Bamboo One tablet and found an interesting bug.
With the tablet connected, I launch Rhythmbox. Whole session crashes and I am
logged off. It seems that X server isn't affected, since other users aren't
logged out.
This happens only with MTP Device
** Attachment added: rhythmbox_mtpdevice_wacom.log
https://bugs.launchpad.net/bugs/663439/+attachment/1701972/+files/rhythmbox_mtpdevice_wacom.log
--
Rhythmbox MTP plugin and Bamboo tablet crash the session
https://bugs.launchpad.net/bugs/663439
You received this bug notification because
** Attachment added: Output of `lsusb -v` with the tablet plugged in
https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/663439/+attachment/1701978/+files/lsusb.txt
--
Rhythmbox MTP plugin and Bamboo tablet crash the session
https://bugs.launchpad.net/bugs/663439
You received this bug
This is still an issue in Lucid Lynx (a regression?).
I have ia32-libs from lucid-proposed (2.7ubuntu26).
I have official 32 bit Firefox build fom Mozilla (for testing
purposes). On start, I get this output:
/usr/share/themes/Ambiance/gtk-2.0/gtkrc:111: error: unexpected identifier
`cellstyle',
Mark: Blacklisting modules is not enough, you have to update initramfs.
See comment #13 and following.
Although I don't have HP Mini, I had the same issues with deadlocks during boot
(comment #17).
Karmic Koala now boots quite reliably for me on Acer AO P531h with Broadcom
4315. I did the
I have the exact same problem with booting stuck on black screen w/ blinking
cursor. The hardware in my case is Acer Aspire One P531h; Ubuntu Karmic 9.10
(UNR). Booting without splash and quiet options revealed the message like:
b43-pci-bridge [...] PCI INT A - GSI 17 (level, low) [...]
This
*** This bug is a duplicate of bug 479597 ***
https://bugs.launchpad.net/bugs/479597
** This bug has been marked a duplicate of bug 479597
HP Mini 311 - Does not always boot
--
Ubuntu unusable - does not boot - b43-pci-bridge
https://bugs.launchpad.net/bugs/459765
You received this bug
This problem appears also in Netbook Edition of Lucid Lynx, Alpha 3,
without Eclipse and Chromium. Once I enable Compositing manager, the
panel disappears after a while. I think it may be related to the
fullscreen launcher.
--
GNOME Panel disappears when compositing manager is turned on and
David Robert Lewis: Sorry, I think your problem is not related to this bug.
Anyway, configuration vm.mmap_min_addr = 0 is already present in your system,
in 30-wine.conf. If this setting is being loaded (check it using command
sysctl vm.mmap_min_addr), it probably doesn't work anymore. Fill the
Friend of mine has a simmilar problem recently with Karmic (ironically,
not with Jaunty) on Asus A6000, SIS M760GX. See how the problem looked
like: http://www.youtube.com/watch?v=yRXVb4F6g6g (wait for the X server
start).
What helped him was the newest SIS driver which you can get in this ppa:
It seems that *any* custom configuration causes installation failure.
In my case, I had to comment out the contents of /etc/sysctl.d/60-local.conf:
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_sack = 1
net.ipv4.tcp_no_metrics_save = 1
net.core.netdev_max_backlog = 2000
These settings are different
hackel is right, Fx 3.5 will be deafult in Karmic.
Denis, update is already done, it is only being tested and as asac on
#ubuntu-mozillateam told me, it should be released today for Jaunty.
More info here:
http://www.asoftsite.org/s9y/archives/160-FAQ-Where-can-I-get-firefox-3.5-for-Ubuntu.html
There is another option, if a missing localization and/or branding is a problem
for you -- check out Ubuntuzilla: http://ubuntuzilla.sourceforge.net/
This nifty script installs official Firefox version by Mozilla into
/opt/firefox/ and takes care of symlinks, DEB diversions and future updates.
NTolerance, lomoco rules are placed in /lib/udev/rules.d/ - although you
are right it shouldn't be that way. Package supplied rules should go to
the /etc/udev/rules.d/. This is yet another (although minor) bug in
lomoco package.
--
lomoco udev rule not working
This seems to be Karmic only release. Is there any plan to backport Firefox 3.5
to Jaunty?
Actually, there is already firefox-3.5 package but it's still Beta 4 (from
March).
--
Please update firefox-3.5 from beta/rc to stable
https://bugs.launchpad.net/bugs/393978
You received this bug
Reopened by Freedesktop, this bug isn't related to any file manager or
desktop environment.
** Changed in: kdebase-runtime (Ubuntu)
Status: New = Invalid
--
OpenType Fonts associated as ODF Template Files
https://bugs.launchpad.net/bugs/338682
You received this bug notification because
I took a look a the filetypes using assoGiate, which clearly shows the problem.
The mimetype application/x-font-otf doesn't have the filename pattern defined,
while the application/vnd.oasis.opendocument.formula-template (which is the
problematic MIME here) does have the filename pattern.
The
In Ubuntu 9.04 rules file was correctly moved to
/lib/udev/rules.d/40-lomoco.rules
But the problem still remains, my MX510 mouse resolution is not set on the
system startup (with edited settings in /etc/default/lomoco). As far as I have
tested, it seems that udev.lomoco script doesn't get
Public bug reported:
Binary package hint: lomoco
In 9.04 (and previous releases) when the computer is resumed from hibernation
or suspension to memory, lomoco doesn't run to set resolution and SmartScroll.
This is possibly caused by udev rule (in /lib/udev/rules.d/40-lomoco.rules)
which is
** Attachment added: script for pm-utils, put inside /etc/pm/sleep.d/
directory
http://launchpadlibrarian.net/27341782/90lomoco
--
mouse resolution is not set on resume from hibernation
https://bugs.launchpad.net/bugs/382229
You received this bug notification because you are a member of
Previously mentioned fix with usb_endpoint is a solution to this bug.
I've attached a patch which directly changes /lib/udev/rules.d/40-lomoco.rules
file.
The rule actually causes lomoco to run twice when the device is
connected, but it's still better than nothing.
I guess there is one more
Public bug reported:
Binary package hint: language-pack-cs
language-pack-gnome-cs-base:
Instalovaná verze: 1:8.10+20081107
Kandidát: 1:8.10+20081107
Tabulka verzí:
*** 1:8.10+20081107 0
500 http://ubuntu.sh.cvut.cz intrepid-updates/main Packages
100 /var/lib/dpkg/status
Sorry for misinformation in my previous comment. Editing
/etc/gdm/Init/Default is still needed, otherwise Num Lock won't
activate on log off.
However, I've noticed strange behaviour of led light with custom
rebuild (it turns off after pressing key after logging in). I will do
more research on this
I can confirm this bug on Ubuntu (GDM/Gnome) Hardy (upgraded from Gutsy). I
didn't have this problem on Gutsy, it has appeared probably after few upgrades
on Hardy.
Rebuilding the numlockx package - as Martin-Éric recommends - fix this problem.
See eg. this page for how to:
See also bug #228196
Shouldn't we mark this as duplicate?
--
gdm and keyboard layout switch
https://bugs.launchpad.net/bugs/228196
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I wonder why the simmilar or maybe the same bug #173721 is marked as
fixed. Adding the configuration into the xorg.conf is a workaround, but
definitely not a fix.
--
[hardy] keyboard layout switching shortcut doesn't work after reboot
https://bugs.launchpad.net/bugs/196277
You received this bug
To Joro Todorov: Have you tried adding it as autostart item? See
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/69
--
[hardy] keyboard layout switching shortcut doesn't work after reboot
https://bugs.launchpad.net/bugs/196277
You received this bug notification because you
Command setxkbmap works fine, but has not effect for me, when I put
it into ~/.bash_profile or even ~/.profile
--
[hardy] keyboard layout switching shortcut doesn't work after reboot
https://bugs.launchpad.net/bugs/196277
You received this bug notification because you are a member of Ubuntu
@Mirza: Thanks, it seems that adding 'setxkbmap' to Gnome's autostart
finally work.
--
[hardy] keyboard layout switching shortcut doesn't work after reboot
https://bugs.launchpad.net/bugs/196277
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Roderick Greening:
Creating new account, setting the keyboard and autologin won't help. I get the
same symptoms.
Reverting to the default xorg.conf will create the same keyboard input section
like in my old xorg.conf, so I think, it won't have any effect. It is very
unlikely that this is
This script should work like the previously mentioned workaround, but keeps
your keyboard settings:
#!/bin/bash
gconftool-2 -s /desktop/gnome/peripherals/keyboard/kbd/options -t list
--list-type=string `gconftool-2 -g
/desktop/gnome/peripherals/keyboard/kbd/options`
The problem is, where to
I can confirm the same symptoms on Hardy with USA and Czech layout, using both
shift keys for switching.
I use autologin in GDM, but problem stays even with timed login set in GDM.
Support for complex characters in Language support in administration is
unchecked.
Editing xorg.conf can probably
I can confirm this bug both on Gutsy and Hardy with Logitech MX510.
I've edited /etc/default/lomoco to use 800cp resolution
(LOGITECH_MOUSE_RESOLUTION=800) but it is not set during startup.
There is possible workaround - see
http://ubuntuforums.org/showthread.php?t=219894 - section 3 (add init.d
Please can you enlighten me as to how I could change the hal script(s)
rather than globally replacing /bin/sh with /bin/bash?
Edit the mentioned script as root. In the script on the first line there is:
#!/bin/sh
Just change this line on:
#!/bin/bash
--
[Edgy] PowerManager has no more effect
35 matches
Mail list logo
