Public bug reported:
lsb_release -rd
No LSB modules are available.
Description:Ubuntu Noble Numbat (development branch)
Release:24.04
This unresolved dependency seems to be the main t64 migration blocker
for the last weeks. I've manually thinned out the dependencies that "apt
upgrad
Public bug reported:
TL;DR: Snap implementation is FUBAR, how do I get back to a non-SNAP
version?
I consider this bug to be Grave since it not only affects thunderbid,
but also a huge number of depending other services, bug-reporting
amongst it.
Thunderbird Snap migration loses user profile
Wi
*** This bug is a duplicate of bug 2056434 ***
https://bugs.launchpad.net/bugs/2056434
On 3/11/24 10:30, Skia wrote:
> Here is how I worked around this:
> * close thunderbird, make sure it's not running in the background
> * `rsync -raxPHAX ~/.thunderbird/ ~/snap/thunderbird/common/.thunderbir
On 3/11/24 17:13, Patrik Lundquist wrote:
> Close Thunderbird.
>
> Remove the new, empty profile.
> rm -r ~/snap/thunderbird/common/.thunderbird
>
>
> mv ~/.thunderbird ~/snap/thunderbird/common/
>
That was my very first test.
Unfortunately it does NOT work for me as described before
and shown in
*** This bug is a duplicate of bug 2056434 ***
https://bugs.launchpad.net/bugs/2056434
@Patrik Lunquist Unfortunately this solution doesn't work for me.
As already shown in my previous post.
In the screenshot attached there you can see the "messenger window"
that opens up when starting thun
@Heinrich: Exactly ONE.
The snapped profile manager doesn't see the profile in the proper place
~/.thunderbird
Snap is causing nothing but trouble. DEB had been working fine since its
inception.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
@Sebastien: Your new push fixed the issue. After the new snap was
installed, I started Thunderbird and it immediately imported the
original profile and started to download the emails from all IMAP
accounts. The locally cached mail folders didn't get copied.
So far things seem to be working but I d
Some modules seem indeed to be 32 bit, I have the same issue
root@kyle:/usr/lib/pulse-2.1/modules# file *| grep -v 64-bit
libprotocol-esound.so: ELF 32-bit LSB shared object, Intel 80386,
version 1 (SYSV), dynamically linked,
BuildID[sha1]=0xba465c853f9f4a756be3c5799004d5dad154d779,
replace
pulseaudio-esound-compat:i386
with
pulseaudio-esound-compat:amd64
and the pulseaudo server will be able to start again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/107854
remove
pulseaudio-esound-compat:i386
and install
pulseaudio-esound-compat:amd64
instead and the pulseaudio server will start again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/10
root@kyle:/var/lib/dkms/nvidia-experimental-310/310.14/build# apt-get install
--reinstall nvidia-experimental-310
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
linux-
On 31.03.2014 18:48, Raj B wrote:
> to clarify, switching off the projector is fine. turning off the
> receiver causes the issue. In all cases, nothing is done to the computer
> itself. It is on and fully operational at all times (i.e., it is never
> suspended / shut down etc.).
What happens when
@Ivan R.: Good to hear, I'll also verify the "CTRL-ALT-F1" - "CTRL-
ALT-F7" workaround next week when I'll have access to my M4800 again.
How is your console configured? Do you boot the kernel with the
"nomodeset" parameter?
--
You received this bug notification because you are a member of Deskto
On 05.04.2014 10:31, Arjen wrote:
> I have the same issue with my HTPC, using a brand new Pioneer receiver
> (and the same with a older Marantz). Switching either of those receivers
> in standby is probably similar to just pulling out the hdmi-plug.
>
> In the Xorg.0.log I see this, when I turn a
Public bug reported:
Please update to 337.19 - Linux kernel 3.15 is not supported with this
old version
[...]
Preparing to unpack .../linux-image-3.15.0-1-generic_3.15.0-1.3_amd64.deb ...
Done.
Unpacking linux-image-3.15.0-1-generic (3.15.0-1.3) ...
Preparing to unpack .../upstart_1.12.1-0ubuntu7
On 24.03.2014 12:33, Marius B. Kotsbak wrote:
> Hmm, I wonder if this is the same I see with my M4800 running 12.04 LTS.
> A workaround for me is typing "CTRL-ALT-F1" and then "CTRL-ALT-F7". Does
> this work for you too?
>
> ** Tags added: precise
>
I can't check before April 7th. I just went on
Public bug reported:
Also affects nvidia-graphics-drivers-319
The effect is identical to
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279
but with Nvidia instead of AMD/ATI drivers.
HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+
display
Once the display
Public bug reported:
TLDR Version:
All current Nvidia drivers get BORKed by ubuntu-drivers-common's gpu-manager
After every reboot (restart of gpu-manager) most links which get set via
update-alternatives are overwritten
Rest:
and look for example like this:
root@charion:/var/lib/dpkg/info# ls
Shutting up gpu-manager by commenting out the upstart config
prevents further corruption of the links.
This is a band aid but at least it lets me continue to work again for
the moment
/etc/init$ diff -uN gpu-manager.conf~ gpu-manager.conf
--- gpu-manager.conf~ 2014-05-28 16:09:45.0 +02
Public bug reported:
lightdm fails to start with 3 connected displays but works 2 displays.
Once lightdm has started and displays the Greeter I can connect the third
display without a hitch.
After logging in I can enable the third display
#!/bin/sh
xrandr --output VGA-0 --off --output DP-6 --of
** Attachment added: "X Server log with 3 displays connected"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1394639/+attachment/4264462/+files/Xorg.0.log.borked
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubunt
lightdm log with 3 displays attached
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.13.0, UID=0 PID=4640
[+0.00s] DEBUG: Loading configuration dirs from
/usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from
/usr/sha
On 20.11.2014 20:55, Andrew P. wrote:
> Since you are using gtk-greeter - can you test version from this PPA?
> https://code.launchpad.net/~kalgasnik/+archive/ubuntu/lightdm-gtk-greeter-background-transition
>
Yes, the new version works fine!
No more fiddling with monitor cables.
Please do not wa
I can confirm that, as of today the latest BIOS for the Dell Precision M4800 is
A09.
The problem still exists with this BIOS version.
BIOS version A10 was made available only for a very short period and then
replaced
again with A09, since it tended to brick the machine.
--
You received this
On 01.12.2014 11:57, Christopher M. Penalver wrote:
> Michael Neuffer, could you please boot into the kernel that comes with
> Ubuntu by default (i.e. not 3.11.x)
What do you mean with "that comes with Ubuntu by default" ?
I currently use 3.16.0-26-generic
> and execute
Public bug reported:
Please check https://bugs.launchpad.net/lightdm/+bug/1190344 for details
and hopefully the fix.
The bug report mentioned above is against Fedora and the fix might not
have made it into Debian/Ubuntu as it seems.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: lightdm 1
On 01.07.2012 12:25, Thomas Hood wrote:
> Has this been fixed in Ubuntu 12.04?
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Incomplete
>
Yes.
But the Network manager has developed another anoying problem:
When the network connection fails (while beeing on the train for
ex
Public bug reported:
root@kyle:/etc/pkcs11/modules# ls -la
total 16
drwxr-xr-x 2 root root 4096 Aug 13 08:43 .
drwxr-xr-x 3 root root 4096 Sep 9 2011 ..
-rw-r--r-- 1 root root 293 Sep 18 2011 gnome-keyring-module
-rw-r--r-- 1 root root 293 Aug 13 02:57 gnome-keyring.module
root@kyle:/etc/pkc
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1036998
Title:
[with fix] gnome-keyring installs duplicate identical config files
gnome-keyring[-.]module
Status in “gnome-keyri
With BIOS A25 and eoan it is still not fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1268151
Title:
[Dell M4800] DPMS support broken, fails to wake up the monitor after
putting
Public bug reported:
System goes to hibernate or suspend even when set to "Don't suspend" on
the Suspend when inactive setting
I use the affected Laptop additionally as a fileserver. The
powermanagement in 11.10 changed in the last few days in a way so that I
can't let the laptop sit without cons
** Description changed:
- System goes to hibernate or suspend even when set to "Don't suspend" on
+ System goes to hibernate or suspend even when set to "Don't suspend" on
the Suspend when inactive setting
- I use the affected Laptop additionally as a fileserver. The powermanagement
in 11.1
On 10/03/2011 10:57 AM, Rodrigo Moya wrote:
> Before setting it, can you please let us know what are the values for
> "sleep-inactive-ac-timeout", "sleep-inactive-ac", "sleep-inactive-
> battery-timeout" and "sleep-inactive-battery"?
>
> You can get the values fromt he command line with:
>
> gsetti
33 matches
Mail list logo
