Public bug reported:
boot up (with wrong time due to bug 1335522). start oclock (with wrong
time). ntpd fixes the time. oclock continues to show the wrong time
until (5 hours later) the correct time catches up with what oclock is
showing.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: x
i was expecting launchpad to allow me to choose to file this bug against
the linux-image package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460006
Title:
e1000e not initialized ~30% of bootups
Public bug reported:
if i watch the nic LEDs while booting they go dark several times, which
i presume to correlate with hardware resets. after each reset, the LEDs
stay out for several seconds, longer than most nics. after the final
reset the LEDs don't come back on until after the system comes
** Package changed: ubuntu => linux-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460006
Title:
e1000e not initialized ~30% of bootups
To manage notifications about this bug go to:
h
perhaps the trigger is when the system boots up with a system time which
preceeds the prior bootup. this sort of thing happens because of
bug#1335522. and that would explain why it happened this time.
imho such time discrepancy should not trigger full lengthy filesystem
checks.
i think this sho
** Attachment added: "grip contigu"|ux.ver" syslog>/tmp/bootups.txt"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1438824/+attachment/4406821/+files/bootups.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
*** This bug is a duplicate of bug 1438824 ***
https://bugs.launchpad.net/bugs/1438824
** This bug has been marked a duplicate of bug 1438824
ALL FSCKs triggered for no apparent reason
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
$ cal
May 2015
Su Mo Tu We Th Fr Sa
1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
31
$ date +"%F %a" -d"today"
2015-05-30 Sat
$ date +"%F %a" -d"yesterday"
2015-05-29 Fri
$ date +"%F %a" -d"last thu"
2015-05-28 T
** Attachment added: "linphone2014-02-24Mon09:35:52.err"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1254880/+attachment/3995262/+files/linphone2014-02-24Mon09%3A35%3A52.err
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "blueman-manager2014-02-24Mon09:35:42.err"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1254880/+attachment/3995258/+files/blueman-manager2014-02-24Mon09%3A35%3A42.err
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Attachment added: "firefox2014-02-24Mon16:07:10.ort"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1254880/+attachment/3995259/+files/firefox2014-02-24Mon16%3A07%3A10.ort
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "xscreensaver2014-02-24Mon15:42:18.ort"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1254880/+attachment/3995264/+files/xscreensaver2014-02-24Mon15%3A42%3A18.ort
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Attachment added: "vncviewer:34:2014-02-24Mon09:40:56.err"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1254880/+attachment/3995263/+files/vncviewer%3A34%3A2014-02-24Mon09%3A40%3A56.err
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
i launched xscreensaver today, which i haven't done for awhile. within
a half hour, the display locked up. likely it's the same bug. and
likely that this bug has been around for many releases. back in natty i
used to run xscreensaver more often, and used to see this bug alot.
today i'm running
alright, i don't *know* it's the same bug today. it certainly isn't a
"lightdm" bug today. Xorg and display drivers are the common elements
of suspect. if y'all would rather i filed today's episode as a separate
bug just say so.
--
You received this bug notification because you are a member of
i should say what leads me to presume they are the same bug is that the
first thing i notice is that the ability to switch VTs is somehow
broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254880
Public bug reported:
sit down at certain computer that runs xubuntu and lubuntu ISOs just fine, but
crashes the kubuntu ISO.
download kubuntu 14.04.1 desktop iso.
boot it.
when the live desktop appears, switch to a virtual console.
type in ubuntu-bug xorg, without a CR, to be ready.
switch back t
Public bug reported:
bluez-simple-agent crashes, in utopic, on a fresh install and fresh
boot. same crash after updating packages and reboot:
$ bluez-simple-agent hci0 00:0C:8A:AA:FE:70 x
Traceback (most recent call last):
File "/usr/bin/bluez-simple-agent", line 127, in
device = adapter.
same in vivid live iso
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1411075
Title:
bluez-simple-agent crashes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
Public bug reported:
most of the installer work already done, behind the crash window the
installer window still said something like installing keyboard
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: ubiquity 2.21.3
ProcVersionSignature: Ubuntu 3.18.0-9.10-generic 3.18.2
Uname: Linux 3.18
Public bug reported:
blueman has paired my headset and connected it to Headset Service,
'pactl list short' shows module-bluetooth-discover is loaded, but
pavucontrol does not show my headset.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: pulseaudio-module-bluetooth 1:4.0-0ubuntu22
ProcVer
btw sometimes it does not crash. i do not know the difference between
when it crashes and when it does not. i can only say when it fails,
calling it repeatedly in sequence seems to keep yielding the same
failure, but at another time, it may work.
--
You received this bug notification because yo
ok perhaps you're right, perhaps the short video confused me, sorry to
bother, many thanks for vlc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413785
Title:
vlc spuriously jumps ahead to next ite
ok, waiting for it to happen again. when i was ready to shutdown both
my vivid boxes last night i just flipped off their powerstrip switches
without logout nor shutdown. this morning, no FSCKs. whatever triggers
them, that's not it.
maybe time discrepancy, if the last OS running had the wrong t
quite unlike mountall, systemd does a good job of scheduling exactly as
many simultaneous FSCKs as i have spindles.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432030
Title:
improper simultaneity
gnome-session 3.14.0-2ubuntu4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1442993
Title:
ctrl not passed to vnc
To manage notifications about this bug go to:
https://bugs.
Public bug reported:
login with gnome, invoke ssh with forwarded port, vnc already running on
remote, invoke vncviewer using forwarded port, control characters typed
locally appear as non-control characters in vnc. login with twm,
everything else the same, works fine.
ProblemType: Bug
DistroRele
apport information
** Tags added: apport-collected ubuntu utopic
** Description changed:
sit down at certain computer that runs xubuntu and lubuntu ISOs just fine,
but crashes the kubuntu ISO.
download kubuntu 14.04.1 desktop iso.
boot it.
when the live desktop appears, switch to a virt
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330322/+files/BootLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409222
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330323/+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/1409222
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330324/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409222
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330332/+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/1409222
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330328/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409222
Ti
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330330/+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/1409222
Title:
kubu
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330331/+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/1409222
apport information
** Attachment added: "xserver.outputs.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330339/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330335/+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/1409222
Title:
ku
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330329/+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/1409222
Title:
kubu
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330337/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409222
Title:
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330327/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330336/+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/1409222
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330333/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/140
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330325/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409222
Title:
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330326/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330338/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409222
Ti
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1409222/+attachment/4330334/+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/1409222
ok, downloaded kubuntu utopic, booted it, the live desktop showed for one half
second, more or less, i tried to switch to vt2, no apparent response (similar
to OP behavior), tried vt3, after several seconds it switched, i installed the
same 2packages as above, and entered the same apport- comman
wow really, 32bit is being abandoned already? only 32bits here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1409222
Title:
kubuntu live desktop iso xorg crashes upon launching installer
To manag
Public bug reported:
i already have the partitions i need, and the swap partition i already
have is already known to other installs, so it'll be a bother to have to
change the fstab and hibernate/restore information for them. my
particular partition layout, in case it matters:
(parted) p all
the install complete and booted, i now see that swap was not formatted,
consistent with as was presented in the partitioning summary. so the
problem here is the misinforming dialog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Public bug reported:
when there's "motion", eg zooming or scrolling, the trail of
intermediate images remain displayed, with a very confusing and amusing
all mixed up result
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: gnome (not installed)
ProcVersionSignature: Ubuntu 3.18.0-9.10-generi
Public bug reported:
on bootup sometimes ALL filesystems are checked. this happens even when
the prior action was an apparently successful shutdown. and this
happens sometimes several times in a row, so clearly has nothing to do
with mount counts. but, it doesn't always happen.
i have 2 vivid
Public bug reported:
all fscks are scheduled and run simultaneously. for those on different
spindles, that would be great. for those sharing a spindle, this is
terribly inefficient. checking all filesystems on this box
simultaneously spends nearly a half hour. when sorted out so that
simultane
"unerased" of course means the areas "underneath" were not
restored/refreshed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1431960
Title:
"motion" leaves unerased trails
To manage notifications ab
Public bug reported:
if /run/screen/S-user exists, kill -chld recreates the fifo.
if /run/screen/S-user does not exist, kill -chld kills screen. this is
not very robust.
if screen can't be bothered to recreate the directory, it could at least
have the courtesy to refrain from destroying itself.
when i login with twm, i get the same thing. windows and icons and
menus are fine, but the root window is never erased/exposed/refreshed.
iirc install was from 2015-01-20 12:04:43 ubuntu/vivid-desktop-i386.iso,
all packages are updated, problem remains, twm or gnome.
--
You received this bug no
in case it's relevant, among the things i deleted were all the /etc and
/usr et al just created by the installer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438328
Title:
/target full, ok, but in
Public bug reported:
trying to install into an existing filesystem, contains data but no /etc
or /usr et al, but apparently not quite enough space. ok, so i opened a
terminal, found some things to delete, made sure not to leave the
terminal inside /target but did leave the terminal open, then dis
sorry, to be clear, not /etc and /usr exactly, rather i deleted inside
/target: etc, usr, var, bin, et al
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1438328
Title:
/target full, ok, but installe
Public bug reported:
this bug has been around since early in vivid devel cycle, both before
and after making systemd the default.
i AM GRATEFUL that systemd DOES know how to properly parallelize all the
fsck processes, activating only one per spindle at all times.
still, i see no apparent reason
all spindles here are MBR. before systemd this was handled by mountall.
if not systemd, what package handles this now? you've labeled this
incomplete, what is needed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
"several times in a row" is ambiguous, sorry, to be more clear, all
filesystems are checked once through per bootup. Or, sometimes, the
bootup is normal (ie does not check all filesystems). whatever triggers
it, checking all filesystems seems to happen several bootups in a row,
then i'll enjoy se
under saucy, satisfyingly, i have lubuntu-desktop and edubuntu-desktop
installed, and can login to lubuntu just fine.
under precise, quantal, raring, AND trusty, however, after installing
both lubuntu-desktop and edubuntu-desktop, logins to lubuntu fail,
either returning directly to the display ma
in precise, this causes my cable box to disconnect. the cable modem
connects with the time wrong, ntp resets the time, dhclient then fails
to renew the lease within the given time, and then Comcast terminates
the connection.
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
install edubuntu-desktop, and then lubuntu-desktop.
on the login screen, click the button to select which desktop to login to.
edubuntu can't be seen, it's off the bottom of the screen.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: edubuntu-artwork 13.10.1
ProcVersion
Public bug reported:
problem 1: fsck column in /etc/fstab is flatly ignored. if the sysadm
wants a particular order of events, she should be able to specify it and have
it heeded. failing that, as a last resort, at least the fstab manpage should
reflect reality.
problem 2: fscks for p
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1248224/+attachment/3900678/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248224
Title:
f
** Attachment added: "this backup of fstab shows the content of the fsck column
that existed at bootup"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1248224/+attachment/3900680/+files/etc%5Efstab%7E6
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
2 fscks (on same disc) running simultaneously on precise.
** Attachment added: "precise ps"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1248224/+attachment/3924514/+files/ps
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Attachment added: "precise fstab"
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1248224/+attachment/3924515/+files/fstab
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248224
Title:
Public bug reported:
vivid:
$ rename.ul -V
rename.ul from util-linux 2.25.2
$ touch a0 b0
$ rename.ul -v 0 1 a0
`a0' -> `a1'
$ rename.ul -v ./b0 ./b1 ./b0
`./b0' -> `./b1'
wily:
$ rename.ul -V
rename.ul from util-linux 2.26.2
$ touch a0 b0
$ rename.ul -v 0 1 a0
`a0' -> `a1'
in words, rename.ul apparently no longer works unless you cd to the
containing directory and omit the dirname portion from the arguments
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466147
Title:
when it fails to rename as in the original example it is silent and
returns code 4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466147
Title:
rename.ul regressed
To manage notifications about th
iirc the install was a gnome devel iso, my best guess was it was a
"settings" issue residual from the gnome install, not a "software or
hardware" issue, i'm guessing it installed some rogue setting value such
that the root window would never be exposed/refreshed, however i no
longer use that instal
Public bug reported:
after pausing vlc for several minutes, and then continuing play, a few
seconds of (probably buffered) play are shown and then play aborts (or
sometimes hangs eating 100%CPU), probably because the network stream has
timed out.
and when play aborts, the playpoint is lost, so no
downloaded xenial-alternate-powerpc.iso on 2016-02-16 at 9:34 CST,
burned to dvd, booted from dvd, requested hfs+ resize from 30gb to 21gb,
resize spent ~2 hours, then got stuck "Starting up the
partitioner...52%", in other words just the same as OP
--
You received this bug notification because y
Public bug reported:
i downloaded current xenial mini.iso midday today (jan28) onto a
powerbook g4, booted via yaboot, selected manual partitioning, requested
shrinking the main hfs+ partition from 30gb to 19gb, it took about 9
hours, then got stuck starting up the partitioner with the progress ba
got this crash merely by installing 12.04 (and checking both download
updates and install 3rd party software) and booting into it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/789733
Title:
check-n
ok, downloaded vivid-desktop-i386.iso dated 2015-02-24 Tue 11:04:11, and
booted it. it is different. the installer launches fine, xorg stays
alive. but icons and buttons are all black, and when hovering over the
taskbar the window previews that popup contain graphical nonsense. in a
terminal i
Public bug reported:
booted up
invoked blueman.
3 devices displayed remaining from yesterday.
try to set "BT15" as "Headset Service". failed.
removed "BT15".
put BT15 in pair mode.
clicked search.
"BT15" reappeared.
pair it. succeeded.
try to set "BT15" as "Headset Service". failed.
removed "BT
didn't netboot fallback to manual net configuration in the past?
the box being installed was the one that serves DHCP. no other DHCP
service available.
so i had to find a different installer to use, either that or setup dhcp
on some other box
--
You received this bug notification because you a
i just found a way to crash it repeatably. open a large file with less,
eg a large /var/log/syslog, and hold down the page down key. xterm will
freezeup quite quickly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
the freezeup doesn't seem to happen unless the window is stretched some,
it will freezeup if it's been stretched to 120x50 and hold down page
down as per previous comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
it occurs to me this could well be a timing issue, having nothing to do
with the specific number of columns or rows, but rather, perhaps, for an
example, on whether input and output happen to collide, and some common
function doesn't handle re-entrance properly..
--
You received this bug notifica
got bluetooth working with linphone by purging pulseaudio&libpulsedsp
and redefining pcm.!default in /etc/asound.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413009
Title:
linphone doesn't wo
it seems under utopic it works fine, while under vivid it works for my
Bose SLIII but crashes for my 8XXPlantronics.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1411075
Title:
bluez-simple-agent c
ok apparently if blueman has already paired the device, then simple-
agent will succeed without crashing. kind of defeats the purpose tho.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1411075
Title:
Public bug reported:
redefining "default" in ~/.asoundrc is ineffective after pulseaudio is
installed. upon removing /usr/share/alsa/pulse-alsa.conf it becomes
possible again. i'm sure we can discuss at length whether this is an
implementation bug or a documentation bug, but either way, it shoul
in vivid it seems slightly different, i have 2 headsets and a bose
soundlink iii, blueman can pair all 3, and all 3 can receive sound
directly via ~/.asoundrc defined devices. however i am unable to send
sound to any of them via pulse, from vlc, mplayer, or linphone. When i
connect either headset
let me revise that, in vivid, gmail (via firefox via google chat) *is*
able to find and successfully use whichever headset is connected to
Headset Service, consistent with it showing up in pavucontrol. yay! it
remains i do not see why linphone won't do that, nor why the bose won't
show up in pavu
Public bug reported:
linphone was working fine with my bluetooth headsets a year ago on
saucy. unfortunately that stopped working with new saucy updates even
before trusty came out, and hasn't worked under on either. here on
vivid, my bluetooth headsets are once again able to pair, be set as
Hea
sorry for the typo, should be "hasn't worked on trusty either."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413009
Title:
linphone doesn't work with bluetooth headsets
To manage notifications ab
Public bug reported:
tmux fails to start while / is readonly. shame, it forces me to use
screen. please just startup anyway. the user can ask for the socket to
be written later if desired by giving SIGUSR1.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: tmux 1.9-6ubuntu1
ProcVersionSign
Public bug reported:
vlc spuriously jumps ahead to the next item in the playlist. take for
example the vlc command below. at spurious times, the video currently
playing will suddenly abort and the next video in the playlist will
begin.
vlc --disable-screensaver \
'http://youtube.com/watch?fmt=
one thought might be that the network connection is spuriously being
lost. but my workaround is to invoke vlc with only a single video at a
time, and doing it that way i never have trouble with it aborting. that
at least gives us a workable vlc, but having a functional playlist would
be nice.
--
things are a little better for me on vivid. my 2 headsets both pair,
will set as Headset Service, show up in pavucontrol, and even work with
gmail(via firefox via google chat plugin)!
still not working: bose soundlink iii will pair, and even work via
~/.asoundrc, but will not show up pavucontrol
i should mention in /etc/bluetooth/audio.conf after [General] i needed to
insert:
Enable=Socket
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1283003
Title:
[Bluetooth + 14.04] Bluetooth headsets a
Public bug reported:
logged in using twm, i used blueman to pair my bose soundlink iii and
set it as audio sink, and pair my plantronics 8xx and set it as headset
service. i'm using mplayer to play radio via alsa /etc/asound.conf
defined pcm to the bose. i've opened linphone merely to test if it
Public bug reported:
same bug as http://savannah.gnu.org/bugs/?35757
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: screen 4.1.0~20120320gitdb59704-9
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architectur
Public bug reported:
whenever there is a power loss or incomplete shutdown, the next
subsequent boot comes up with the system time set such that the local
time shows the time that would be correct for the UTC time, until such
time as ntpdate or ntpd get a chance to correct the system time.
this m
201 - 300 of 461 matches
Mail list logo
