Public bug reported:
Binary package hint: aumix
1) Run aumix.
2) observe aumix eat shit.
3) run strace aumix
** Affects: aumix (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
aumix dumps core in Ubu 6.10
https://bugs.launchpad.net/bugs/107767
You received this bug
** Attachment added: crash output
http://librarian.launchpad.net/7351778/_usr_bin_aumix.65792.crash
--
aumix dumps core in Ubu 6.10
https://bugs.launchpad.net/bugs/107767
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I have the same symptom, using the nvidia driver (version x86-100.14.09)
and feisty (7.04).
I am still able to ssh into the box, and the Xorg was just hung.
Killing it keeps me from having to hard boot the whole box, but that's
just a workaround, obviously. What other information can I provide?
** Attachment added: my dpkg -l output
http://launchpadlibrarian.net/8100774/pkglist
--
Feisty freezes upon Logout or Switch user
https://bugs.launchpad.net/bugs/118605
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Public bug reported:
Binary package hint: kdemultimedia
After an installation of Intrepid Beta on my MacBook Pro (Santa Rosa), I
installed pommed so I could use the sound buttons on it. However, it didn't
appear to work at all, except that it caused the current volume to be displayed.
I used
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/18466300/Dependencies.txt
--
kmix + pommed doesn't work as expected on MacBook Pro (Santa Rosa) with
Intrepid Beta
https://bugs.launchpad.net/bugs/282305
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Binary package hint: nvidia-glx-177
Using the hardware drivers manager in Kubuntu Intrepid Beta, I installed
nvidia-glx-177. After restarting, kdm failed to start. I had to comment
out the following lines in xorg.conf:
Section Module
Loadglx
Disable dri2
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/18467216/Dependencies.txt
** Attachment added: LsMod.txt
http://launchpadlibrarian.net/18467217/LsMod.txt
** Attachment added: LsPci.txt
http://launchpadlibrarian.net/18467218/LsPci.txt
** Attachment added:
Here's the xorg.conf I modified.
As for the logs, they probably don't contain any useful information
because I disabled the nvidia driver before filing the bug report.
** Attachment added: Modified xorg.conf
http://launchpadlibrarian.net/18476992/xorg.conf
--
nvidia-glx-177 on MacBook Pro
Wow, this report got really old. :)
I don't use Intrepid anymore, and I have no idea whether this was resolved. At
this point, I don't think anyone cares, so whoever is in charge can close this
bug.
--
kmix + pommed doesn't work as expected on MacBook Pro (Santa Rosa) with
Intrepid Beta
Doesn't work for me either. I installed systemd-shim/saucy-proposed,
rebooted, suspended, waited 15 minutes and turned it on again - wifi
didn't work. sudo killall NetworkManager still solves the problem, so
no regression.
--
You received this bug notification because you are a member of Ubuntu
For me the PPA does not work but I do NOT use TLP. However, I do use
Jupiter http://wiki.ubuntuusers.de/Jupiter which is supposed to
increase battery life (and actually does that pretty well). Also I used
powertop once to fix all the items it offered.
--
You received this bug notification
This is actually a big problem for two reasons:
(1) The user does not get the correct feedback to the problem: Instead of a
notice that the certificate not trusted, he/she is just asked again and again
and again for the correct username and password.
(2) Encouraging people to trust in central
just coming in: Google found french office spying with CA signed
intermediate certificate:
https://code.google.com/p/chromium/issues/detail?id=326787 and
http://www.heise.de/newsticker/meldung/Google-erwischt-franzoesische-
Behoerde-beim-Schnueffeln-2062479.html
So please stop requesting CA
I don't have the time to repeat the experiments, however in my case it
seems to be pretty deterministic: None of the suggested ways works
(menu, pm-suspend, the other command or lid-close, which i usually do).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
In the other bug report, I said that sudo pm-suspend didn't work,
which is wrong. Maybe I forgot to re-activate the network after some
previous test ...
So my current results are (tested 5 times):
All of these methods:
- closing the lid
- using the Unity menu - Suspend
- sudo gdbus call -y -d
pm-suspend.log after unsuccessful suspend-resume-cycle (i.e. network
didn't work afterwards).
** Attachment added: pm-suspend.log
https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+attachment/3912649/+files/pm-suspend.log
--
You received this bug notification because you
I just modified
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service in the way
you asked. Then I suspended using the Unity menu. However, the laptop never
turned off (usually it does after 20-30s) - at least not for over a minute. So
I pressed I key and was able to login (and
Public bug reported:
My ThinkPad X220 with Ubuntu 13.10 (upgraded from previous versions)
takes 20 seconds or more to suspend. This wasn't the case with 13.04.
During those 20 seconds I can reactivate the screen (which turns off
properly) and then login and use the laptop (until it suspends
It currently doesn't work for me. I have the latest saucy-proposed
packages, should the update you mentioned be in there?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing
Is there any chance this (and https://bugs.launchpad.net/ubuntu/+source
/pm-utils/+bug/1253456) might get fixed in the next months, e.g. for the
next LTS release? I would have to downgrade to Ubuntu 12.04 otherwise
(or maybe stick to Windows?).
--
You received this bug notification because you
Thank you for your answer. I will try to do that, however I don't know
much about D-BUS. I managed to activate the system bus logging and dbus-
monitor outputs a lot now. However that's too much for my console
window and it is without timestamps. How can I get a useful logfile that
I can upload
I attached a logfile (without timestamps, because I don't know how) that
was recorded during sudo gdbus call -y -d [...], 30 seconds of
waiting, resuming the computer from standby and entering the password.
** Attachment added: logfile for sudo gdbus call -y -d
I have 6-0ubuntu0.13.10.
Please see the attached nm.log that I created as Martin described in #82.
I had to wait some time after sudo Networkmanager ... until my wifi was
connected. Then I suspended which took the usual while. After resume, the
network was disconnected as usual. I didn't have
And here's my systemd-shim.log (see Martin's comment #88). Just like
Christian, I do not have to press Ctrl+C, it exits a few moments after
resuming and entering the user password.
** Attachment added: Suspended using Unity menu
The workaround does not work on my machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1252121
Title:
missing PrepareForSleep signal after resuming, causing networking to
stay disabled
To
Same here (13.10) . The big problem is that it seems to be in all releases, so
downgrading from 13.10 to the previous LTS release wouldn't even help. Half a
year ago, everything was fine. So why is it that now it suddenly does not work
anymore and can't be fixed (e.g. by reverting some
This bug still occurs on my device,
** Changed in: systemd-shim (Ubuntu)
Status: Expired = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1253456
Title:
Suspend takes 20 seconds
To
A reinstallation might help. Even though the bug has not been fixed for the new
LTS version (), a fresh installation might help. I didn't do much testing
because I uninstalled Ubuntu to free up my SSD space for Windows (which runs
rather stable and doesn't give a whole bunch of error
Since yesterday I am also massively affected by this issue (Ubuntu
19.04, Dell Latitude 7280). The mouse buttons 'stop working' every few
minutes, making working for me very tiresome.
The only gnome extensions I have active are the frippery move clock,
system monitor and desktop icons.
Shortly
Ok, I solved the problem in my case. Given it seemed to be a
communication problem I go the idea it could be ownership of sockets. I
found various folders in my home directory were not owned by my local
user and/or were not readable. Root owned .dbus and .gvfs, below .local
were files/folders
The same always happens to me when the system does not register key-
strokes from my Apple bluetooth keyboard after a system restart.
Keyboard appears as connected in the bluetooth setting, but no
keystrokes come through. syslog fills with these errors.
Setup: MS bluetooth mouse and Apple
> doesn't happen on xubuntu with the indicator
But it does happen on Ubuntu.
> The priority is low for Ubuntu since there is no report of such
problems on Ubuntu
Here comes that report. To reproduce:
1. Download the latest Ubuntu (21.04, live stick is enough).
2. Download and open Joplin
In my case (Ubuntu 20.04.1), update-notifier was being spawned every
time I log in (regardless of my software update settings) due to this
file:
/etc/xdg/autostart/update-notifier.desktop
This file has a "X-GNOME-Autostart-Delay=60", causing a 60-second delay,
so from a user's perspective it
> I believe that this should be fixed by this upstream commit, which
will be in the 5.12 kernel
Has anyone been able to verify that? If it indeed fixes this annoying
issue (I get notifications about low mouse battery all the time even
though it's almost full), then it might be worth back-porting
On a different machine (no Nvidia) but with the same monitor, I can also
reproduce this over DisplayPort but not over HDMI.
So I don't think that the Nvidia graphics card/driver is to blame.
Instead, it seems like there's a general DisplayPort-related issue
either in Linux/Alsa or in my
Public bug reported:
When I play YouTube videos, then in the quiet parts of the video (i.e.
in pauses between sentences, even if they are very brief), I hear a
popping/crackling sound on my headphones connected through my
DisplayPort monitor and my Nvidia GeForce GTX 745 card (I have this PC:
37 matches
Mail list logo
