Created attachment 142084
dmesg from old MacBook running lubuntu 18.04
Same problem here on an old MacBook running lubuntu 18.04.
A good workaround is adding "video=SVIDEO-1:d" to the grub kernel
parameters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: samba (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/750786
Title:
nmbd job fails to start on boot
To manage notifications
On Ubuntu 14.04 nmbd fails to start on boot. There may be a regression in the
upstart script.
The following change fixed the problem for me:
Change the start on condition in /etc/init/nmbd.conf to:
start on (started smbd)
(Thanks to Dan Corso who proposed this fix in comment #49 in bug
** Changed in: samba (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/750786
Title:
nmbd job fails to start on boot
To manage notifications about this bug
On Ubuntu 14.04 nmbd fails to start on boot. There may be a regression in the
upstart script.
The following change fixed the problem for me:
Change the start on condition in /etc/init/nmbd.conf to:
start on (started smbd)
(Thanks to Dan Corso who proposed this fix in comment #49 in bug
It is now well over a month since this bug has been marked as fixed. Is
this ever going into precise and/or quantal, or will this version of
gvfs only be available from raring onwards?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
libsecret-1 from proposed works very well and fixes the issue for me as
well. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071055
Title:
vinagre crashed on connecting to vnc
To manage
*** This bug is a duplicate of bug 961549 ***
https://bugs.launchpad.net/bugs/961549
Why is bug #961549 private? Marking a public bug as a duplicate of a
private bug does not make a lot of sense to me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The missing package is gstreamer0.10-alsa. See bug #932141.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/844345
Title:
pitivi complain about one of osssink or alsasink missing
To manage
This problem is still there with oneiric.
** Tags added: oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932141
Title:
pitivi doesn't work out of the box without gstreamer0.10-alsa
To
** Branch linked: lp:ubuntu/natty/libwebcam
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/811604
Title:
uvcdynctrl spams uvcdynctrl-udev.log and fills up filesystem
To manage notifications about
This also happens with a perfectly good USB connection when vmware-
player is starting a Vista guest.
The information about having enabled a workaround for a driver issue is
not that important that it has to be written to the log file millions of
times. It should be sufficient to log the problem
Woudn't it be great to move the blacklist out of the C code into a
configuration file?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770625
Title:
overlay-scrollbar_0.1.9-0ubuntu1 update causes
@Michael: I checked gvfs-1.6.4 (used in Maverick) and 1.8.0 (Natty).
This part of the code has not changed since 1.6.1. However, this only
affects files on remote locations.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm the problem reported by Lesley Harrington still exists with
gnome-control-center 1:2.32.0-0ubuntu2 on a new maverick system (installed and
updated today).
--
Can't save dual monitor configuration
https://bugs.launchpad.net/bugs/631217
You received this bug notification because you
If you do not want to change your termcap file, you can also change your
main menu entry or launcher to
gnome-terminal --geometry=132x43
or whatever you like.
--
can't define a default geometry in the preferences
https://bugs.launchpad.net/bugs/641616
You received this bug notification
I can confirm that the fix proposed in Casper's link works (Lucid,
amd64). The original location is here:
http://forums.opensuse.org/english/get-help-here/applications/409465
-fix-gdesklets.html
--
gdesklets does not start
https://bugs.launchpad.net/bugs/83922
You received this bug
*** This bug is a duplicate of bug 641616 ***
https://bugs.launchpad.net/bugs/641616
** This bug is no longer a duplicate of bug 646179
gnome-terminal does not follow the terminal size specified in gconf
** This bug has been marked a duplicate of bug 641616
can't define a default
*** This bug is a duplicate of bug 641616 ***
https://bugs.launchpad.net/bugs/641616
** This bug has been marked a duplicate of bug 641616
can't define a default geometry in the preferences
* You can subscribe to bug 641616 by following this link:
If the install is still not complete, you could check the installation status
of the fglrx packages: dpkg -l | grep fglrx
Everything should have ii in the first column.
If the ati control center does not start from the menu, what error
messages occur (if any) when trying to start amdcccle from a
I had the same problem and managed to fix it:
1. sudo gedit /usr/src/fglrx-8.771/2.6.x/kcl_ioctl.c
Navigate to the end of this file.
Change the line causing the problem
from:
return compat_alloc_user_space(size);
to:
return arch_compat_alloc_user_space(size);
2. Run a terminal
cd
Oops. In step 4 I forgot the sudo in front of the dpkg commands. You
probably figured this out yourself.
--
fglrx module does not build on 2.6.35-22-generic
https://bugs.launchpad.net/bugs/640866
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This seems to be fixed. Debug symbols for kernel 2.6.32-24.38 are
present.
--
dbgsym packages being reaped - newest package from Mar 24
https://bugs.launchpad.net/bugs/579805
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I tried to test with the latest kernel from http://kernel.ubuntu.com
/~kernel-ppa/mainline/daily/current/.
I noticed that the file 'linux-source-2.6.35_2.6.35-999.201006151505_all.deb'
is only 2.2K. That doesn't look good to me.
However, the other files have a reasonable size and the kernel
Public bug reported:
An up to date Lucid system (2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3
19:31:57 UTC 2010 x86_64 GNU/Linux) crashes when starting a Windows
guest in VMware-player.
A 120MB crash file is created. Unfortunately apport fails to upload
this, that's why I am filing this bug
** Attachment added: log.txt
http://launchpadlibrarian.net/50444827/log.txt
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/50444376/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/50444377/AplayDevices.txt
** Attachment added:
Why has this been set to won't fix so fast? The ongoing discussion
about this issue clearly shows that different people have different
preferences. So the most logical choice seems to make the behavior
configurable:
- No confirmation dialog at all (i.e. shut down immediately)
- A confirmation
I have just discovered that the dialog can already be switched off
(option apps/indicator-session/suppress_logout_restart_shutdown in
gconf-editor). So it's just the timer option that is missing.
--
Shutdown timer no longer appears
https://bugs.launchpad.net/bugs/548415
You received this bug
*** This bug is a duplicate of bug 327872 ***
https://bugs.launchpad.net/bugs/327872
I can't see the duplicity with bug #327872, but I would say that it's a
duplicate of bug #502642.
--
*.ts video detected as application/x-linguist MIME type
https://bugs.launchpad.net/bugs/207672
You
On an up-to-date 10.04 LTS system (which has shared-mime-info
0.71-1ubuntu2) I can still see a strange phenomenon:
*.ts files on a local hard disk are recognized fine (MPEG-2 transport stream).
*.ts files on a network share (SMB on a XP host) are still recognized as
application/x-linguist.
What
@Oliver: That works, thanks.
I would like to note that my
/usr/share/mime/packages/freedesktop.org.xml has no mime-type
text/vnd.trolltech.linguist with an alias application/x-linguist,
just a plain entry for a mime-type application/x-linguist. Moving that
XML element down towards the end did the
Just for the records, with gvfs-1.6.1 it's not possible to include the file
content in the mime-type evaluation process.
Only the filename is passed to the relevant libglib function.
--
.ts files always get recognized as application/x-linguist and never as
video/mp2t (mpeg transport stream)
My box crashes while booting a Vista image in VMware player.
It is an ASUS P5Q-E mainboard. lspci output is attached.
** Attachment added: lspci.txt
http://launchpadlibrarian.net/47916336/lspci.txt
--
empathy cause kernel-panic when executed
https://bugs.launchpad.net/bugs/495577
You
See also bug #344079. The _new_imp() takes at most 4 arguments (5
given) message described there appears on Lucid-rc (amd64) when trying
to run gdesklets shell.
--
gdesklets cannot start, looking for tiling module
https://bugs.launchpad.net/bugs/569714
You received this bug notification because
34 matches
Mail list logo
