*** Bug 484305 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/335761
Title:
Placement policy 'Remember' by default for all windows
To manage
Public bug reported:
Ubuntu version: Ubuntu 20.04.3 LTS
Nautilus version: 1:3.36.3-0ubuntu1.20.04.1
Overview:
Nautilus appears to move files to Trash when deleting files, regardless of what
drive it happens on. This threw me off for a bit as I never expected deleted
files to be moved into
I encountered the similar issue since 1.9.1-1ubuntu0.4 update. On the
previous version 1.9.1-1build1, if I run a CPU stress test, the fan will
keep going up until full speed (~6000rpm) as the temp rises. On
1.9.1-1ubuntu0.4, the fan sometimes is kept at 3600rpm or remains at
zero. Once CPU reaches
I see that the feature that it seems to conflict with is the `[homes]`
section in /etc/samba/smb.conf (which makes it so that every user's home
directory is exported as a share), so maybe commenting out that whole
section and restarting samba might do the trick.
See
Reassigning this to samba, this can't be fixed in nautilus-share
** Package changed: nautilus-share (Ubuntu) => samba (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915674
Title:
Sharing
a valid system user name
Well it sounds like you can't have a share with the same name as a
username, and there's a `games` user in Ubuntu by default. Pick another
share name perhaps?
--
Kind regards,
Loong Jin
--
You received this bug notification because you are a member of
>Status: Unknown
>
> ** Tags added: focal groovy hirsute packaging
>
> ** Changed in: geany-plugins (Ubuntu)
>Status: New => Confirmed
I've merged the pull request locally, testing the build now. I'll make
an upload soon.
affects ubuntu/geany-plugins
status triag
** Changed in: geany (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909026
Title:
Ubuntu 20.04 and 20.10 package out of date
To manage notifications about
Ubuntu releases don't get new upstream releases after the Ubuntu release
has gone out. Use the PPA if you want newer versions of Geany:
https://launchpad.net/~geany-dev/+archive/ubuntu/ppa.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
yoo_si_jin@bigboss:~$ sudo apt upgrade
[sudo] password for yoo_si_jin:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
Public bug reported:
I am using ubuntu mate 21.04 daily build.I tried updating with sudo apt
update && sudo apt upgrade -y && sudo apt dist-upgrade -y && sudo apt
autoremove -y
I saw version update of linux image from 5.8.0-25-generic
to
1.linux-image-generic/hirsute-proposed
Public bug reported:
On the System76 Lemur Pro, the fan rgularly turns off at lower
temperatures (anything below 60°C), and `sensors` reports 0 RPM.
When this happens, the fan speed status in tmux gets stuck at the last
non-zero value. Looking in /dev/shm/byobu-*-*/status.tmux/, I see a
Is this fix going to be released? Or, abandoned? I got a
XPS-13-7390-2-in-1, and was waiting for the release of this fix. If
necessary, I may want to provide a test.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
status fixcommitted
https://salsa.debian.org/geany-
team/geany/-/commit/f98c497b894663698b547c44c47d2ec0cff5b691
** Changed in: geany (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
me too. - 14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752721
Title:
package sensible-utils 0.0.9 failed to install/upgrade: package
sensible-utils is not ready for configuration cannot
resolved
sudo apt install sensible-utils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752721
Title:
package sensible-utils 0.0.9 failed to install/upgrade: package
sensible-utils is not ready
Same with me.
GL63 8RE / DualBoot with Windows 10 (Window is fine)
Internal Speaker not working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812693
Title:
[MSI GL63 8RE, Realtek ALC1220] No
** Bug watch added: github.com/geany/geany/issues #1846
https://github.com/geany/geany/issues/1846
** Also affects: geany via
https://github.com/geany/geany/issues/1846
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Just confirmed, it does happen in 18.04.
** Changed in: fwupd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753655
Title:
fwupd doesn't release hidraw
] https://github.com/geany/geany-plugins/pull/677
[2] http://launchpad.net/~geany-dev/+archive/ppa
--
Kind regards,
Loong Jin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768412
Title:
Some plugins
Geany 1.32-2 (in bionic) is built with gtk3.
** Changed in: geany (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1424194
Title:
geany gtk2 has too
Public bug reported:
cant install and system crash
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python-scour 0.26-3build1
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
Public bug reported:
fwupd doesn't release hidraw devices for unplugged peripherals, causing
the kernel to keep allocating new hidraw devices until it hits
HIDRAW_MAX_DEVICES.
Steps to reproduce:
1. Ensure that fwupd.service is running
2. Plug in a Logitech Unifying Receiver (or any other thing
Alright, looks like it's fixed for both.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573577
Title:
QR code image does not generate after upgrade to Ubuntu 16.04
To manage notifications about
It works in GNOME Shell (and the code for this plugin hasn't changed in
years), so I think it's related to the way unity uses its own settings
daemon that isn't quite the same as gnome-settings-daemon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
+ === Begin SRU Boilerplate for Ubuntu ===
+
+ [Impact]
+ python-qrencode is currently broken for all users in xenial due to the
removal of Image.fromstring from pillow. The fix is to replace all calls to
Image.fromstring with Image.frombytes.
+
+ qreator is also
*** This bug is a duplicate of bug 1573577 ***
https://bugs.launchpad.net/bugs/1573577
** This bug has been marked a duplicate of bug 1573577
QR code image does not generate after upgrade to Ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Sorry, slipped my notice that Xenial was still affected. It's fixed in
Ubuntu 17.04 onwards.
John, which version of Ubuntu are you using?
** Changed in: python-qrencode (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: qreator (Ubuntu)
Status: Confirmed => Fix Released
**
*** This bug is a duplicate of bug 1573577 ***
https://bugs.launchpad.net/bugs/1573577
Hmm, as far as I can tell, Qreator 16.06.1-1 and python-qrencode 1.2-1
are no longer affected by this bug. This means that it should be fixed
in Ubuntu Zesty (17.04) upwards. I guess that leaves.. Xenial?
Okay, works for me.
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Test Case]
+
+ Try to launch Slic3r. If affected by this bug, it crashes immediately
+ with this message:
+
+ Your vendor has not defined OpenGL macro GL_MULTISAMPLE, used at
+ /usr/lib/slic3r-prusa/Slic3r/GUI/3DScene.pm line 998.
+
+
+ [Regression Potential]
+
+
It's a harmless warning. Don't worry too much about it.
** Changed in: slic3r (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498966
Title:
slic3r
signee: (unassigned) => Chow Loong Jin (hyperair)
** Changed in: slic3r (Ubuntu Artful)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726103
Title:
pansge:~$ slic3r-prus
** Bug watch added: GNOME Bug Tracker #789634
https://bugzilla.gnome.org/show_bug.cgi?id=789634
** Also affects: gnome-shell via
https://bugzilla.gnome.org/show_bug.cgi?id=789634
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
The key repeat runaway also happens occasionally in urxvt when the CPU
is sufficiently loaded, but can be recovered by hitting the key in
question again, and doesn't lead to GNOME Shell hanging.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
GNOME Shell running in Wayland completely hangs when the key repeat rate
is sufficiently high and used inside Chromium and/or Google Chrome. Then
GNOME Shell, at-spi's dbus-daemon, ibus-daemon, and chromium-browser all
get stuck at 100% CPU. GNOME Shell's RSS also quickly
p mounts.
Could you obtain a stack trace of nautilus to identify the real reason for the
crash?
See https://wiki.ubuntu.com/DebuggingProgramCrash for more information.
status incomplete
--
Kind regards,
Loong Jin
** Changed in: nautilus-share (Ubuntu)
Status: New => Incomplete
--
You
** Changed in: geany (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723236
Title:
geany plugin manager cannot be enabled
To manage notifications about this
On Fri, Oct 13, 2017 at 04:41:25PM -, Hans Joachim Desserud wrote:
> ** Tags added: xenial
>
Looks like you need to have plugins enabled that have settings in the first
place. Try enabling the tree browser plugin for instance.
--
Kind regards,
Loong Jin
--
You received th
Public bug reported:
I've been running a locust[1]-based web load test on my Ubuntu machine
running GNOME Shell (wayland). When starting a new test with a client
spawn rate of ~500/s, it issues a huge amount of getaddrinfo() calls.
When using libnss-resolve, this causes a huge number of
Tested and verified on xenial, yakkety and zesty.
** Tags removed: verification-needed verification-needed-xenial
verification-needed-yakkety verification-needed-zesty
** Tags added: verification-done verification-done-xenial
verification-done-yakkety verification-done-zesty
--
You received
Yeah I tested it using mediainfo on a large file in chroots of the
target distributions without rebuilding mediainfo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693850
Title:
libzen wasn't
** Package changed: banshee (Ubuntu) => rhythmbox (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1176510
Title:
gstreamer-1.0/libgsttypefindfunctions.so has a segmentation fault
To manage
Whoops, uploaded with a wrong version number (0.4.34-1ubuntu0.16.04.1)
to zesty. I've fixed it with another upload (0.4.34-1ubuntu0.17.04.1).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693850
** Description changed:
- The switch to cmake caused two compilation flags to be accidentally dropped:
+ The switch to cmake caused two compilation flags to be accidentally dropped:
-D_LARGE_FILES -D_FILE_OFFSET_BITS=64
This causes all file-handling operations in zenlib to fail to work
** Also affects: libzen (Ubuntu Artful)
Importance: Undecided
Assignee: Chow Loong Jin (hyperair)
Status: Fix Released
** Also affects: libzen (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: libzen (Ubuntu Zesty)
Importance: Undecided
Status
This bug was fixed in the package libzen - 0.4.35-1
---
libzen (0.4.35-1) experimental; urgency=medium
* [015b0fa] Imported Upstream version 0.4.35
-- Chow Loong Jin <hyper...@debian.org> Tue, 04 Apr 2017 00:39:46
+0800
** Changed in: libzen (Ubuntu)
Status: T
- mediainfo
- mediaconch
This has been fixed in
https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855.
** Affects: libzen (Ubuntu)
Importance: Undecided
Assignee: Chow Loong Jin (hyperair)
Status: Fix Released
** Tags: patch
** Description changed
It works:
In [1]: import qrencode
In [2]: qrencode.encode_scaled('foo', 1)
Out[2]: (1, 21, )
** Tags removed: verification-needed
** Description changed:
+ [Impact]
+ python-qrencode is currently broken for all users in yakkety due to the
removal of Image.fromstring from pillow.
+
+ The fix is to replace all calls to Image.fromstring with
+ Image.frombytes.
+
+ [Test Case]
+ Run the following script and see if it ends in
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587249
Title:
PIL exception fromstring
To manage notifications about this bug go to:
** Changed in: python-qrencode (Ubuntu Yakkety)
Status: New => Confirmed
** Patch added: "debdiff for yakkety SRU"
https://bugs.launchpad.net/ubuntu/+source/python-qrencode/+bug/1587249/+attachment/4804699/+files/debdiff.patch
--
You received this bug notification because you are a
Fixed in zesty.
** Changed in: python-qrencode (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: python-qrencode (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: python-qrencode (Ubuntu Yakkety)
Assignee: (unassigned) => Chow Loong Jin (hy
** Changed in: telegram-app
Assignee: (unassigned) => Jin (jin.cth)
** Changed in: telegram-app
Status: In Progress => Fix Committed
** Changed in: telegram-app
Milestone: None => m34
--
You received this bug notification because you are a member of Ubuntu
Bu
** Changed in: telegram-app
Status: Fix Committed => Fix Released
** Changed in: telegram-app
Assignee: Jin (jin.cth) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
The patch we provided is landed and verified with rc-proposed.
Paste the device info here:
current build number: 573
device name: mako
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2016-11-18 15:11:10
version version: 573
version ubuntu: 20161118
version
** Changed in: telegram-app
Milestone: m33 => m34
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460464
Title:
Add support for the OPUS audio format
To manage notifications about this bug go
** Tags added: ota-14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460464
Title:
Add support for the OPUS audio format
To manage notifications about this bug go to:
nautilus-share sets up your computer to host shares, not to access
shares. Reassigning to nautilus.
** Package changed: nautilus-share (Ubuntu) => nautilus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package mediaconch - 16.08-1
---
mediaconch (16.08-1) unstable; urgency=medium
* [56e1e87] Imported Upstream version 16.08
-- Chow Loong Jin <hyper...@debian.org> Thu, 01 Sep 2016 23:35:18
+0800
mediaconch (16.07-1) unstable; urgency=
This bug was fixed in the package mediainfo - 0.7.88-1
---
mediainfo (0.7.88-1) unstable; urgency=medium
* [9ea5e69] Imported Upstream version 0.7.88
-- Chow Loong Jin <hyper...@debian.org> Thu, 01 Sep 2016 23:35:20
+0800
mediainfo (0.7.87-1) unstable; urgency=
This bug was fixed in the package libmediainfo - 0.7.88-1
---
libmediainfo (0.7.88-1) unstable; urgency=medium
* [4017389] Imported Upstream version 0.7.88
-- Chow Loong Jin <hyper...@debian.org> Thu, 01 Sep 2016 23:06:29
+0800
libmediainfo (0.7.87-1) unstable; urgency=
his is something I noticed after
Jerome said that mediainfo might not have been able to access the file.
--
Kind regards,
Loong Jin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619933
Title
://bugs.launchpad.net/ubuntu/+source/libmediainfo/+bug/1619932
Changelog entries since current yakkety version 16.03-2:
mediaconch (16.08-1) unstable; urgency=medium
* [56e1e87] Imported Upstream version 16.08
-- Chow Loong Jin <hyper...@debian.org> Thu, 01 Sep 2016 23:35:18
+0800
mediaconch (1
sync at
https://bugs.launchpad.net/ubuntu/+source/libmediainfo/+bug/1619932
Changelog entries since current yakkety version 0.7.84-1:
mediainfo (0.7.88-1) unstable; urgency=medium
* [9ea5e69] Imported Upstream version 0.7.88
-- Chow Loong Jin <hyper...@debian.org> Thu, 01 Sep 2016 23
0.7.85-1build2:
libmediainfo (0.7.88-1) unstable; urgency=medium
* [4017389] Imported Upstream version 0.7.88
-- Chow Loong Jin <hyper...@debian.org> Thu, 01 Sep 2016 23:06:29
+0800
libmediainfo (0.7.87-1) unstable; urgency=medium
* [36d49df] Imported Upstream version 0.7.87
-
** Changed in: telegram-app
Importance: High => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460464
Title:
Add support for the OPUS audio format
To manage notifications about this
** Changed in: telegram-app
Milestone: None => m33
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1460464
Title:
Add support for the OPUS audio format
To manage notifications about this bug go
@Vicamo,
Many thanks for your update,
just confirmed "...not about the password...",
after discussed.
Also I can see such the symptom in settings -> WiFi,
not affect to OOBE only, so the subject need to be changed,
from "...in OOBE WiFi list" to "...in WiFi list".
Besides,
after reset to
Hello Lukas,
Exactly, never ever feed the password but it shows "Connected" directly.
It is quite easy to reproduce after reset-to-factory or image flashed,
by the way, I can confirm this issue in krillin, frieza and midori as well...
--
You received this bug notification because you are a
The symptom can be reproduced in OOBE,
this is why I mentioned in subject of this bug and the meaning of "first boot".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604322
Title:
The SSID gets
Hello Lukas,
Please see the reproducing steps I stated above,
no password pre-saved for that.
Which means the boot is the first boot,
no any password stored and the user just see the dialog for asking,
the first beginning password but the status shows "Connected".
It does not make sense
Public bug reported:
Description:
The wifi AP get connected directly in OOBE,
when user is starting to input the password.
Reproduce Steps:
a) Boot the Ubuntu device to enter the OOBE
b) Select one of the wifi ap in the SSID list
c) Observe the connection status of the SSID behinds
I am sure,
since the number of results > 10 as I configured.
You could use Today aggregator to see the results from Holidays scope here:
https://code.launchpad.net/~todayscope-team/today-scope/trunk
https://code.launchpad.net/~holidays-scope-team/holidays/trunk
The Holidays is shown by
Public bug reported:
Description:
When scope users vertical-journal as its layout, sometimes it shows the button,
but sometimes it does not, not sure which one is the correct behavior.
Reproduce Steps:
a) Implement a scope with a vertical-journal layout
b) Observe the scope showing
Please help us to confirm it since it could be reproduced by 100%.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1593035
Title:
Scope category layout: vertical-journal does not follow the value of
Public bug reported:
Description:
Scope vertical-journal layout does not follow the value of collapsed-rows.
Reproduce Steps:
a) Implement a scope with category-layout: vertical-journal
b) Add collapsed-rows property, for instance "collapsed-rows": 1
c) Observe the showing of the
Did you hold the shift key down? On a qwerty keyboard, you need the
shift key or you get [Ctrl+=] instead.
** Changed in: geany (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: telegram-app
Status: Fix Committed => Fix Released
** Changed in: telegram-app
Assignee: Jin (jin.cth) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Changed in: telegram-app
Status: Fix Committed => Fix Released
** Changed in: telegram-app
Assignee: Jin (jin.cth) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Changed in: telegram-app
Milestone: None => m30
** Changed in: telegram-app
Assignee: (unassigned) => Jin (jin.cth)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1582173
Title:
M
Bug fixed,
and verified pass on developer side.
The change list is submitted as rev. 187,
below is the detail information.
http://bazaar.launchpad.net/~libqtelegram-team/telegram-app/telegram/revision/187
Device Information:
current build number: 439
device name: mako
channel:
Merge proposal sent,
please see below for detail:
https://code.launchpad.net/~libqtelegram-team/telegram-app/app-very-slow-great-lag-after-update-2.2.4/+merge/294728
** Changed in: telegram-app
Assignee: (unassigned) => Jin (jin.cth)
** Changed in: telegram-app
Sta
Since Telegram is suffering on the APL asynchronous mode and its performance,
we have below branch to re-implement the converged UI with synchronous APL,
this is a temporary solution for the lagged Telegram:
the gconf
> folders, if you're still interesed in tracking down the problem...
The gconf folder in question sounds useful, yeah. Please attach that to the bug
report.
--
Kind regards,
Loong Jin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Odd. I can't see what's going on from the logs. Could you move
~/.config/banshee-1/banshee.db elsewhere and try again?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1567441
Title:
Banshee UI ALWAYS
** Changed in: telegram-app
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554621
Title:
Invalid use of palette apparent with new SDK
To manage
Looks like you're on Xenial, not Wily.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1534971
Title:
banshee freezes on start
To manage notifications about this bug go to:
Thanks for testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1534971
Title:
banshee freezes on start
To manage notifications about this bug go to:
On Sun, Apr 03, 2016 at 07:11:20PM -, Francois Noel wrote:
> I tested the patch and it fixes the problem on Wily (up to date as of
> April 3rd).
>
> I was able to rescan the library completely. Exit Banshee. Restart
> Banshee without a long freeze.
>
> @Chow Loong Jin,
On Tue, Apr 05, 2016 at 09:24:55AM +0800, Chow Loon
g Jin wrote:
> On Sun, Apr 03, 2016 at 07:11:20PM -, Francois Noel wrote:
> > I tested the patch and it fixes the problem on Wily (up to date as of
> > April 3rd).
> >
> > I was able to rescan the library comple
Sounds like something's leaking file descriptors. Could you run "lsof -p
-n" a couple of times while it is scanning, but before it
crashes?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1489419
** Changed in: telegram-app
Milestone: None => m28
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554621
Title:
Invalid use of palette apparent with new SDK
To manage notifications about this
** Branch linked: lp:~libqtelegram-team/telegram-app/lp1554621
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554621
Title:
Invalid use of palette apparent with new SDK
To manage notifications
Hmm, that new patch does look correct.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1534971
Title:
banshee freezes on start
To manage notifications about this bug go to:
** Changed in: telegram-app
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554621
Title:
Invalid use of palette apparent with new SDK
To manage
Debug output please. http://banshee.fm/contribute/file-bugs
status incomplete
--
Kind regards,
Loong Jin
** Changed in: banshee (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Debug output please. http://banshee.fm/contribute/file-bugs
status incomplete
--
Kind regards,
Loong Jin
** Changed in: banshee (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Could you upload the log directly after reproducing this bug please?
Here are instructions: http://banshee.fm/contribute/file-bugs/
** Changed in: banshee (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello Ethan,
Please find attached one Kyle pushed,
thanks.
** Attachment added: "com.canonical.scopes.photos-local_1.27_armhf.click"
https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1384243/+attachment/4574199/+files/com.canonical.scopes.photos-local_1.27_armhf.click
--
You
1 - 100 of 2831 matches
Mail list logo
